Entitlements.plist versus Appname.Entitlements

Question

I'm implementing APNS (iOS5, Xcode4) into an application and I'm getting the error:

"The executable was signed with invalid entitlements."  

Research on SO and google is telling me to use Entitlements.plist but I already have Appname.Entitlements, the keys seem to be pretty much identical, and unless I'm missing something adding an Entitlements file is gone from the new file templates.

So What is the difference between these two? Do I need to just add a plist name "Entitlements"?

Also to verify:

-- My provisioning profile supports APNS. -- I am using the correct Distribution profile. -- I'll be doing an Enterprise distribution.

Answer 1

According to Technical Note TN2250 you should just remove the entitlements file.

If you are defining a custom Code Signing Entitlements file within your Target > Build Settings, you might try removing that configuration entirely and rebuilding/resubmitting. More often than not, Code Signing Entitlements are defined unnecessarily. You only need to specify a custom Code Signing Entitlements file if your application is utilizing custom keychain access sharing or iCloud. Otherwise, remove the Code Signing Entitlements configuration from all build configurations on your Xcode project's Target > Build Settings, the rebuild and reattempt your submission/validation.