On solving the Invalid Entitlements error message with building to a device.
On solving the Invalid Entitlements error message with building to a device.
- Subject: On solving the Invalid Entitlements error message with building to a device.
- From: Alex Zavatone <email@hidden>
- Date: Mon, 27 Aug 2012 18:16:29 -0400
I just took an older project and moved it over to our build machine running Xcode 4.3.2, did a build to an iOS 5.1 device and of course, "This application was signed with Invalid entitlements" message shows up.
Of course, there are no entitlements in the project, searching for them on the project shows this to be the case.
To the best of my knowledge, I've never manually placed an entitlement on anything, nor can I find one
so, I'm thinking that this is one of those error messages that is a red herring.
I happen to have 3 other projects on the dev box that do build to that iOS 5.1 device.
On StackExchange, there are many examples of "delete your provisioning files and try again" but those examples don't mention why Xcode seems to think that there are some entitlements somewhere that are invalid.
I just tried changing my code signing to what the other projects are using, changed the bundle identifier from my personal account to the corporate account on the Target, thinking that possibly, the bundle identifier being associated with my personal account could have caused this.
The app builds and copies over to the device, but never runs, always with the same entitlements error.
Changing each of the code signing settings (for the device) to test every code signing option I have, finally, I get a long error that explains that the file can not be launched because a file can not be found and there is a path to a file on the Mac's HD, since the file does not exist on the device. I look and it's there.
So, I press it to launch. It launches just fine.
Now, every time if I delete the app from the device and run with the code signing that used to generate entitlements errors, the app installs to the device, but I have to manually launch it because of the missing file error.
Better than nothing.
But the original question remains. Even if your project has no entitlements that you are are of, are there hidden entitlements somewhere?
And if so, or if not, just what conditions tend to trigger this error message?
In my searches, I have seen many cases of "do this to fix it", but no explanations why the message comes up in the first place.
If we can (or if someone already has) figured this out, it certainly be eye opening and might serve to help a bunch of people who run in to error messages like this that don't point the user in a direction that would help to solve the problem.
Cheers.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden