The executable was signed with invalid entitlements

Question

I am having a problem with ad-hoc distribution on my iPhone. I have developed an application with SDK 3.0. I have a developer's license. I have added certificates and provisioning profiles in my project. So, no problem with that.

But, when I try to install the app on my iPhone, it compiles the project and then displays the error: "The executable was signed with invalid entitlements" in the Organizer window. Am I missing something? I have upgraded my iPhone from 2.2.1 and have downloaded latest SDK from Apple.

Please help me with this issue.

John · Answer 1 · 2011-07-07T21:23:04.370

52

There are pretty good instructions in the 'Portal Program'. If you log into

http://developer.apple.com/iphone

Then click Distribution on the left, and click the

Creating and Downloading a Distribution Provisioning Profile for Ad Hoc Distribution

link at the bottom.

Here's the key bit:

For Ad Hoc Distribution, complete the following:

In the File Menu, select New File -> iPhone OS -> Code Signing -> Entitlements. Name the file “Entitlements.plist" and click ‘Finish’. This creates a copy of the default entitlements file within the project.
Select the new Entitlments.plist file and uncheck the “get-task-allow” property. Save the Entitlements.plist file. (in Xcode 4, get-task-allow is called "Can be debugged" )
Select the Target and open the Build settings inspector. In the ‘Code Signing Entitlements’ build setting, type in the filename of the new Entitlements.plist file including the extension. There is no need to specify a path unless you have put the Entitlements.plist file somewhere other than the top level of the project.
Click ‘Build’. (Note: Your binary must contain a flattened, square-image icon that is 57x57 pixels. This icon is displayed on the iPhone or iPod touch home screen.)

edited Jul 07 '11 at 21:23

answered Jul 02 '09 at 15:56

John

1,549
1
13
15

1

I was just going to write the same thing, it's easy to forget you need the get-tak-allow for ad-hoc in addition to store builds! – Kendall Helmstetter Gelner Jul 02 '09 at 16:44
This didn't work for me — it resulted in the same "invalid entitlements" error. But based on some comments below, I cleared everything, and then CHECKED (not unchecked) "get-task-allow", and tried again -- this time it worked. – Joe Strout May 25 '10 at 16:04
I had this same problem with an old project that I updated from git-hub, and checking that property (when I recall it was previously unset) also seemed to cure my issue as well. Strange. – TimM Jun 15 '10 at 03:53
2

Wow, that just saved me about 12 hours of head-banging. Thanks. – JayCrossler Jun 29 '10 at 14:03
3

Thanks for this, surprising how this stuff is so hard to find on Apple's site, it seems SO is a better resource. – KevinDTimm Oct 19 '10 at 12:28
@KevinDTimm Actually, it's not surprising. The documentation uses anchors very poorly and as a result, is not easily referenced by URI. That's why you see so many posts about provisioning and IOS on SO that describe going to a URI and then "click here, click there, click anywhere". I look forward to the day when Apple's documentation is not a walled garden. – David Watson Apr 03 '15 at 19:48

score 34 · Answer 2 · answered Jul 05 '11 at 12:35

This error also may occur if you're trying to profile an app where the device is not included in the provisioning profile.

Make sure your device is included in the dev provisioning profile you want to use. Somehow the error message is misleading. My entitlements were actually ok.

score 14 · Answer 3 · answered Jan 26 '10 at 17:14

14

I have found that "get-task-allow" needs to be checked for Development builds but unchecked for Distribution builds. The easiest way to accomplish this (AFAIK) is to have two entitlements files in your project: Entitlements.plist and EntitlementsDebug.plist - and to reference the proper one in the build project settings for the various configurations in your project.

answered Jan 26 '10 at 17:14

gumbypp

159
1
2

10

I have *never* needed to do this. For your development build configuration, just make sure that Code Signing Entitlements is blank. – Ben Scheirman Aug 03 '10 at 16:15
2

get-task-allow unchecked worked for me... what a sneaky little bastard – WrightsCS Oct 06 '10 at 03:06
I too had to check get-task-allow to get a developement build on my device. – memmons Oct 27 '10 at 00:25

score 6 · Answer 4 · edited Jul 02 '17 at 10:03

6

Code signing entitlements are no longer necessary for Ad Hoc builds in Xcode 4 - see details notes in Apple Technical Note TN2250

edited Jul 02 '17 at 10:03

Cœur

37,241
25
195
267

answered Aug 11 '11 at 20:20

snibbe

2,715
1
27
34

score 5 · Answer 5 · answered Oct 19 '10 at 12:19

If you once come into the situation, that checking "get-task-allow" seems to be required in order to deploy your debug (!) build to your phone, check this:

a) Check the build setting. There should be no entry in "Code Signing Entitlements" for Debug b) Remove Entitlements.plist temporarily and build your debug version. If it complains about a missing Entitlements.plist, then you probably have the same situation, I had to fight today. c) Build again with Entitlements.plist and enable "get-task-allow". If it works now, you probably have the same problem:

After messing around with new profiles I couldn't deploy my Debug build to the phone. AdHoc was fine. I checked a) - empty.. Hmm. I checked b) - complains. c) - worked...

After all I examined project.pbjproj in an editor and - although the GUI did claim, that there was no entry for "Code Signing Entitlements" in fact there was one in the Debug section. I emptied it and was done.

This worked for me. After I added an Entitlements.plist for AdHoc, xcode copied that requirement to my Debug and Release targets (although I did not enter that in the Build tab). After removing from the pbxproj file by hand, the Debug build works again. — thrusty, Mar 17 '11 at 17:27

score 4 · Answer 6 · answered Jun 25 '13 at 10:02

4

This is because your device, on which you are running your application is not selected with your provisioning profile.

So just go through Certificates, Identifiers & Profiles select your iOS Provisioning Profiles click on edit then select your Device

enter image description here

answered Jun 25 '13 at 10:02

Rajneesh071

30,846
15
61
74

score 3 · Answer 7 · answered Dec 14 '10 at 03:28

I have just had an exciting three hours battling with this. I have just upgraded a project to 4.2 and for some reason it just wouldn't work.

I eventually removed the Entitlements.plist file and then created a new one.

File > New File > Code Signing > Entitlement

Name the file Entitlements.plist

Make sure it's in the Resources group in xCode.

It didn't put in the get-task-allow BOOL type in the Entitlements.plist file. I added it, checked it, saved it, unchecked it, saved it. This made me feel better.

I then removed the Adhoc and Release profiles I had created. Re-downloaded them from the Provisioning Portal and droped them back into the xCode organizer.

I then went into Build Settings and made sure the correct profiles were assigned to the Debug and Release profiles.

I then changed the to Release / Device. Hit the build button and it worked.

I have no idea why.

score 1 · Answer 8 · answered Oct 08 '09 at 22:22

1

John's answer is 99% correct. I found that (at least in my configuration), you have to open the Build settings inspector for the PROJECT. The build settings for the target do not contain "Code Signing Entitlements". Perhaps this doesn't make a difference if you have only one target in your project. But if you have multiple targets, you need to go to the project build settings. In any case, after doing what John said, my ad-hoc distribution build worked perfectly.

answered Oct 08 '09 at 22:22

iisystems

1,089
1
11
12

1

That's odd, because I have Code Signing Entitlements under the Target settings in XCode 3.1. – Simon Woodside Oct 16 '09 at 00:26
Code Signing Entitlements will appear if you make the Base SDK iPhone Device not Simulator in the target. – Steve Weller Nov 21 '09 at 00:41

score 1 · Answer 9 · answered Apr 01 '14 at 17:13

In Xcode 5.1, if you go into Preferences -> Accounts -> View Details...

Make sure the Signing Identity status is Valid. If it says Revoked, hit the Plus button and add the appropriate signing identity: iOS Development or iOS Distribution. Xcode will replace it with a new, valid one.

score 1 · Answer 10 · answered Sep 09 '14 at 14:26

1

For me that solved it: https://coderwall.com/p/-ckobg

Open Project.xcodeproj > project.pbxproj
Remove all lines like these:
1. PROVISIONING_PROFILE = ...
2. "PROVISIONING_PROFILE[sdk=iphoneos*]" = ...
3. CODE_SIGN_IDENTITY = ...
4. "CODE_SIGN_IDENTITY[sdk=iphoneos*]" = ...
Set provisioning profiles & code signings for the target again

answered Sep 09 '14 at 14:26

Robert

431
7
19

This solved my problem. It was specifically the line `CODE_SIGN_IDENTITY = ...` that caused the problem. I have no idea when this was added by Xcode, or if I did it by mistake myself, but what a mess. Compared to other IDE's I have had so many weird problems with Xcode. I try to avoid it and stick to AppCode. – Tobiaswk Jun 26 '15 at 08:04

score 0 · Answer 11 · answered Oct 23 '12 at 16:15

I was trying to add iCloud support to my existing app, but found that after adding entitlements and configuring iCloud, my app would no longer debug.

I realised that my generic iOS development certificate had a different APPID from the app I was working on. So to fix it, instead of using my generic certificate I created a specific development certificate for that APPID.

I refreshed my provisioning profile in XCode, cleaned out the app, disconnected my device, restarted XCOde and connected device and ran, and it now works a treat!

score 0 · Answer 12 · answered Nov 29 '12 at 15:46

I also spent several hours fighting with this as well. The fix is real simple. Edit your Entitlements.plist file in the root of your project's directory. Find the line that says <key>get-task-allow</key>. Underneath it should be <false/>. Change that to <true/>.

score 0 · Answer 13 · answered May 04 '13 at 14:19

Sorry that this is very late, but I just was looking at this question and found something that worked for me. I went to PROJECT->Build Settings and found the Code Signing section. Beside debug, my distribution profile that said Iphone Distribution: MY NAME was selected. I instead selected Iphone Developer: MY NAME on the drop-down list under IpodProfile (for bundle identifiers com.myName.myApp which was the provisioning Profile for my device. Hope this helps!

score 0 · Answer 14 · answered Mar 17 '14 at 12:34

0

I just had this happen to a developer on the team I administer.

It turned out his developer certificate expired and after renewal, I neglected to add his certificate to the provisioning profile his app used. enter image description here

answered Mar 17 '14 at 12:34

sean808080

242
4
13

score 0 · Answer 15 · answered Jul 15 '14 at 06:15

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.

score 0 · Answer 16 · answered Oct 24 '14 at 17:21

Had this issue occur when everything seemed to be setup correctly, build setting were pointing to correct provisioning profile, code signing was properly setup, etc.

Issue occurred because I had just created a new scheme and hadn't regenerated my CocoaPods for the new configurations. As you can see from the image, the new ad-hoc configuration is pointing to the Pods.production configuration, instead of a Pods.ad-hoc configuration (and test respectively)

Demonstrating a mis-match of ad-hoc configuration and scheme configuration

To fix:

Set the offending configuration to None -- cocoapods wouldn't generate the configs unless I did this
Close XCode
Run pod install
Re-open XCode and set the new scheme's configurations to the newly generated configurations.

That's it!

score 0 · Answer 17 · answered Sep 09 '11 at 10:18

pJosh, this might help understanding. In my case, my Team Provisioning Profile was expiring (the Provisioning Portal indicated it is managed by XCode), as well as the device testing profile for the app. (I still don't know why, but the portal had a "Renew" button next to the team profile, but it wouldn't do anything when I clicked it.)

So, I deleted the profiles about to expire, then in XCode go to Organizer (Command-Shift-2), under Library / Provisioning Profiles, I deleted the expiring ones. Then click "Refresh" at the bottom, enter my Apple ID, and it renewed the expiring ones.

Finally, on my Target, I went to Build Settings, Code Signing, and made sure to select the provisioning profile. Voila, now it builds to my device.

score 0 · Answer 18 · answered Jan 16 '12 at 04:48

Just got this same error code. It seems there are different things that cause this and therefore different ways to fix it.

In my case, I had two different devices with the same name (an iPhone 4 and an iPhone 4S). Changing the name of one of them fixed this error completely for me...

score -1 · Answer 19 · answered Jan 06 '13 at 14:45

-1

Check if you're device is included in the provisioning profile.

answered Jan 06 '13 at 14:45

Steve Ham

3,067
1
29
36

The executable was signed with invalid entitlements

19 Answers19

Linked

Related