The entitlements specified…profile. (0xE8008016). Error iOS 4.2

Question

I am getting the \'dreaded\' error The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning pr

Answer 1

I had the same problem in my app, after a few month this specific app worked fine.

The problem was that the Capabilities configured in my Xcode project (under Targets -> {ProjectName} -> Capabilities) were not the same as the Capabilities configured in the provisioning profile (you can check that in the Apple member centre under Identifier -> App Ids -> {your app ID}. In the member centre I saw that Game Center is enabled and so in my project I also enabled Game Center. Then the app was able to launch.

I don't know how it worked until now. That's still a mystery :)

Answer 2

I had this issue with Xcode 4.2.1.

For me it was nothing to do with Entitlements file, or Ad-hoc...

I was returning to and old project, and I'd forgotten to add my new iPhone to the provision.

Silly mistake, but also a silly corresponding error message... :-/

Answer 3

Deleting the xcuserdata folder solved my issue. More on that here: https://stackoverflow.com/a/9968884/300694

Answer 4

Happened to me on Xcode 8, it was partially caused by the new Provisioning Profile build setting, as in this Xcode version there are two entries for provisioning profile:

• Provisioning Profile
• Provisioning Profile (Deprecated)

My fault was that I updated only the first one, and the deprecated entry was still pointing to an invalid provisioning profile. Changing both to the same value solved the issue (clearing the deprecated entry should also have the same effect).

Answer 5

The code I was working on had a different bundleid in the Info-plist than in the Product Bundle Identifier build setting.

I found this because I noticed this message in the device console in the devices view:

MIS: entitlement 'application-identifier' has value not permitted by provisioning profile 'iOS Team Provisioning Profile: com.xxx.yyy'

Answer 6

I've had this issue with the iCloud entitlements. My problem was that I forgot to enable iCloud for my App ID in the Provisioning Portal.

After enabling iCloud for your App ID, you will need to recreate the provisioning profiles.