This package is not valid. Apple does not currently accept applications created with this version of the OS. (Mavericks)

Question

To begin with, I installed Mavericks, I was curious to see new features ... It would be better to wait, because (apparently) there are no sensational changes.

In any case, I try to send my application to the application store, but after a serious struggle with code signatures, I received a message:

"This package is not valid. Apple does not currently accept applications created with this version of the OS."

.... From what I read, the only solution seems to remove the Mavericks and go back to Mountain Lion, but I will be happy if anyone has an alternative solution.

Answer 1

After some research on the Internet, I found a fix for this problem.

1) Open the "Application Store" and leave it now.

2) press cmd + shift + g on your desktop and go to / system / library / coreservices /

2) Copy SystemVersion.plist to the desktop, and duplicate the file

3) Open the file with the correct name on the desktop, and not with the copy, and replace the old part with the following:

<key>ProductBuildVersion</key> <string>12E55</string> <key>ProductCopyright</key> <string>1983-2013 Apple Inc.</string> <key>ProductName</key> <string>Mac OS X</string> <key>ProductUserVisibleVersion</key> <string>10.8.4</string> <key>ProductVersion</key> <string>10.8.4</string> 

4) Now copy this edited file to / system / library / coreservices and go to the "App Store" application.

5) Download Xcode 4.6.3, now you can, because your OsX is detected as Mountain Lion.

6) After downloading its completion and installing Xcode, reboot.

7) Open the project in beta version of xcode 5, if you have some .xib files, go to the file inspector, check the document version and change the development version to 4.6 instead of 5. Do this for each .xib, then close xcode 5

8) Open Xcode 4.6.3 and restart your project. Check build settings that 10.9 are not present anywhere. Replace it with 10.8 or whatever you need.

9) Clean, create for archiving, archive ... Swipe!

10) Now your project should be checked.

11) After you have downloaded the application, rename SystemVersion.plist (copy) to your desktop and copy it back to / system / library / coreservices. You do not need to reboot.

It's kind of a hack, but if you don't want to reinstall everything, this is the only way to go.

Ps: after replacing SystemVersion.plist, you will notice strange behavior in Os, such as safari, which does not work, and so on, so I suggested duplicating the plist file before changing the version of os. In any case, if you can still use the terminal and "vi" to restore everything, if for some reason you have not copied the original.

Hope this helps someone. I lost a day finding out a solution;)

Answer 2

A similar build issue of 13A3017 on Mavericks switched it to 13A603 and it worked.

Faster to use this command in the terminal and just remember the original assembly number, then to switch it back.

sudo nano / System / Library / CoreServices / SystemVersion.plist

but probably first you need to make a copy of the file just in case

Answer 3

I had this problem when I used Mavericks 10.9.1 (build 13B40) and Xcode 5.1 dp. I will finally solve the problem:

• Use Xcode 5.0.2 instead of Xcode 5.1 dp.
• Go to /system/library/coreservices/ and modify SystemVersion.plist using copy / paste as @Benz's answer. Thanks @Benz
• After copying and supporting SystemVersion.plist modify the contents as follows:
  • mod ProductBuildVersion up to 13A603 , which is the assembly number of Mavericks 10.9.0 GM.
  • mod ProductUserVisibleVersion and ProductVersion up to 10.9.0
• Replace SystemVersion.plist using the one you changed.
• Restart Xcode.
• Restore and run the application.
• Submit.
• Succeed !!!
• Restore SystemVersion.plist with the source file you executed.

Answer 4

If you don't want to use SystemVersion.plist in bulk, here is another way to go through 10.10 :

Once you have created the archive, you can change the package .app and .plist in the root of the archive so that it matches the valid receiving version. Then use Xcode to send it. There is no need for mass use with code signatures or an application loader.

If you want a simple solution and don’t mind paying for it, I created a tool to do it with ease: https://vox.vg/xcarchiver/