Despite having many apps approved often on the first attempt, I am now hitting this error over and over:
"2.14 The following issue was found:
The application has been set to the minimum OS to be “10.7.0”, it should be “10.7”
I am using Xojo Release 2014 Release 1.1 and mini app wrapper. I have set the system requirements to 10.6.6, but Apple keeps insisting I am setting it to 10.7.0, but I am not. I just double checked the plist it does indeed say 10.6.6. The only real change is that I upgraded from Mavericks to Yosemite since my last development spurt.
[quote=144535:@M Jacques]Despite having many apps approved often on the first attempt, I am now hitting this error over and over:
"2.14 The following issue was found:
The application has been set to the minimum OS to be “10.7.0”, it should be “10.7”
I am using Xojo Release 2014 Release 1.1 and mini app wrapper. I have set the system requirements to 10.6.6, but Apple keeps insisting I am setting it to 10.7.0, but I am not. I just double checked the plist it does indeed say 10.6.6. The only real change is that I upgraded from Mavericks to Yosemite since my last development spurt.
:/[/quote]
Build without APW
copy info.plist to your disk
Modify it in a text editor to comply
Use a CopyFile to put it back in the bundle after build, and before AW Mini.
since january apple rejects apps that are not minimum 10.7
if you specify 10.6.6 it will surely be rejected
and “10.7” is not the same as “10.7.0”
did you try to edit the plist in your app to write “10.7” only ?
Some time ago I added checks in App Wrapper for verifying the bundle identifier, I used Apple’s Property List documentation. However I received so many complaints, and Apple allowed all these bundle identifiers that the documentation recommended against, I gave up. Maybe they’ve started to enforce their rules?
What’s the bundle identifier that they’re rejecting?
It’s not a Xojo issue, many others have submitted Xojo apps just fine (including myself.)
Check the .pkg you create before you upload it (not just the app installed by it)
Also check that you’re selecting the latest version when submitting for review and not selecting an old one.
I swear, it is such a tiny little app to cause so much grief.[/quote]
The pkg is not signed, but all the pkg utilities I have floating around say the minimum os version of that .pkg is set at 10.8
Thank you for the quick response. I never realized packages are signed, too. I made this Xojo 2014 Release 1.1 and App Wrapper Mini. I used Xojo '14 Release 1.1 and App Wrapper Mini for three apps this summer and they were all fine when I uploaded them to the Mac App Store. How do I sign a package?
I just noticed App Wrapper Mini has an option for “Apple Recommended Format” Do you think this would do the trick? Apparently, I was using hybrid format before.
The package is signed, but it’s the App Store submission certificate, not Apple’s App Store distribution, which is why it doesn’t open on our machines.
The LSMinimumSystemVersion is “10.8”. Everything looks fine to me.
I can only think that the problem is because they’ve messed around with iTunes connect, for messing around’s sake. In the product info page, you need to remove the existing build and attach another build. When you upload a build to Apple it just gets piled in the ‘Pre-release’ section, until you then alter the product information and swap the build. I don’t know if you’ve done that already or not.
It confused me, I have an application with several uploads in the pre-release section because I didn’t realize this myself.
[quote]I can only think that the problem is because they’ve messed around with iTunes connect, for messing around’s sake. In the product info page, you need to remove the existing build and attach another build. When you upload a build to Apple it just gets piled in the ‘Pre-release’ section, until you then alter the product information and swap the build. I don’t know if you’ve done that already or not
It confused me, I have an application with several uploads in the pre-release section because I didn’t realize this myself.[/quote]
This must be it. I must have selected the same old build over and over again, This is embarrassing. Major fail on Apple’s part for not making this apparent.
