invalid entitlements 0xE8008016 when I add the entitlements file

Question

I\'m trying to do ad hoc distribution. When I use XCode, the application installs fine on my phone.

In preparation for ad hoc distribution, I created the default entitl

Answer 1

I had not agreed to the new updated licensed agreement from apple.

Briefly : Please log in to your developer's account -> profile's -> review -> read the agreement or get your lawyer read it for you -> agree (at your own will) -> and again click profile's to check the status of your profile.

In my scenario the valid code signing entity was not showing up. When i followed the above procedure it was visible and i was able to run the app on the device and/or create the iPA file without much difficulty.

Answer 2

You need to follow these steps

• Have you changed the bundle identifier in your project's info.plist???

Please make sure that this also matches with your provisioning profile's identifier.

• go to your projects info. select the configuration you want your build to be deployed then check in build settings that you have added the dist.plist file and the provisioning profile is the same thta you need to run with.

• If you are making the build for distribution then set the get-task-allow mark as unchecked

Hope this helps.

Answer 3

Do the following steps:

1. Remove the provisiong file from the Xcode -> Organizer
2. Download again from your developer account. Make sure that you have downloaded profile from distribution tab.
3. Drag and drop that profile to Xcode
4. Change the bundle identifier of your plist that match with your provisioning profile App ID.
5. Go to application setting target and active target and choose your profit from there.
6. Now rebuild and run the app.

Answer 4

It's also worth noting that this problem may be rooted in trying to install properly authored programs on Jailbroken devices. At least in my case, all my development units and I kept getting this error. By adding the get-task-allow BOOL type to a Entitlements.plist file, I still got the error but the files were installed on the devices (live debugging doesn't work though).

Answer 5

I found I had to add the new device I was testing on to my Provisioning Profile, on the IOS Provisioning Profile Site.

Answer 6

Removing the entitlement wasn't and option for me as I wanted to use "iCloud", so after digging a little I found that the problem was that "iCloud" not being enabled on the app configuration on the "iOS Provisioning portal".

Enabling it and regenerating the provisioning did the trick for me.