Geek Answers Handbook

Xcode 4.1 - archiving application gives me Entitlments.plist error

I am using Xcode 4.1 and MacOSX Lion 10.7. I am trying to archive my application for Mac, so I can upload my application to iTunes connect, but it gives me this error:

ProcessProductPackaging / Developer / Platforms / MacOSX.platform / Entitlements.plist / Users / username / Library / Developer / Xcode / DerivedData / appname / Build / Intermediates / appname.build / Debug / appname.build / appname.xcent cd "/ Volumes / Applications / iOS / Mac app store / appname "embedded productPackagingUtility / Developer / Platforms / MacOSX.platform / Entitlements.plist -entitlements -format xml -o / Users / username / Library / Developer / Xcode / DerivedData / appname / Build / Intermediates / appname.build/Debug/appname.build/appname.xcent

error: list of properties for reading errors '/Developer/Platforms/MacOSX.platform/Entitlements.plist' - the list of properties does not have an object Failed to execute the builtin-productPackagingUtility command with exit code 1

This error does not occur if I do not sign the code. I was able to send my applications properly before migrating to Xcode 4.1. I can not find any documentation on how to sign the application in xcode 4, and I have no idea what new permissions are Enable and the sandbox.

When I somehow earn it, I receive this email from iTunes with the following error: Invalid code signing rights. The rights to sign your application package do not correspond to those contained in the provisioning profile:

According to the initialization profile, the package contains a key value that is not allowed: "appname" for the key "com.apple.application-identifier" in appname.app/Contents/MacOS/appname

What do I need to do to properly send the application to iTunes?

+4
source share
2 answers

It turns out that a problem with application packaging occurs if you use a new Macbook released after June 2010. To pack the application, follow these steps:

1) Creation and archiving

2) Open Organizer - Archives, find a new archive.

3) Right-click the "Show in Finder" archive

4) Right-click the archive in the search engine to "Show package contents"

5) expand your application (> Products / Applications / YourApp)

6) Right-click your "Show Package Contents" application

7) Delete the _CodeSignature directory

8) Edit Info.plist

a) Change BuildMachineOSBuild to "11A511" b) Save, close

9) Return to the Products / Applications / YourApp directory in the search engine

10) Open Keychain Access.app

  a) Find your certificate "3rd Party Mac Developer Application: Your Name" b) double click to inspect it c) Copy the full Common Name "3rd Party Mac Developer Application: Your Name"

11) Open a terminal and enter the following:

  codesign -s "<paste your cert common name here>" -fv <drag the archived app from the finder to the terminal window here>

12) check the output:

  "...path to app...: replacing invalid existing signature" "...path to app...: signed bundle with Mach-O universal (i386 x86_64)"

13) Close all windows.

14) Open Organizer - Archives in Xcode

15) Confirm ... yep.

16) Send ... yay!

+2
source

This method really worked for me too!

It was my mistake, iTunes Connect kept kicking it, not giving up ... just throwing it away almost instantly. One way or another ... this method worked for me! Now the application is in review. Like he said, Yay!

Invalid code signing rights. Your application package signature contains code signing rights that are not supported on Mac OS X; this can happen if your Mac OS X project has been ported from iOS. Check the configuration of the Xcode project code signing rights and remove any unnecessary rights.

In particular, key "key-key groups" in [YourAppName] are not supported. Invalid code signing rights. Your application package signature contains code signing rights that are not supported on Mac OS X; this can happen if your Mac OS X project has been ported from iOS. Check the configuration of the Xcode project code signing rights and remove any unnecessary rights. In particular, the "application-identifier" key in [YourAppName] is not supported.

I just want to add there ... that I also had a black MacBook, which was released before 2010 ... I still went ahead and added the "BuildMachineOSBuild" key to "11A511" as indicated in the instructions. :)

0
source

More articles:


All Articles