Automatic signing is unable to resolve an issue with the "projectName" target's entitlements file

Question

I am new to mac and i am getting this error as below

What should i do i have bought the developer licence and i created the provisioning certificate but still i am facing this issue. i am not sure why i am getting this error any help.

i have followed this youtube link inorder to create a provisioning profile and distrubution profile https://www.youtube.com/watch?v=Xh2nnjttOwo&t=367s

UPDATE

after updateing my buildsettings like this below

and i am getting new error like this

ofcourse i tried that one but still same issue @jigneshVadadoriya — Mohan Gopi, May 15 '17 at 06:50
Have you enable anything under your target > capabilities?. You should enable same in your app id in developer account. — ChintaN -Maddy- Ramani, May 15 '17 at 06:54
inside `target>capabilities` ?? i have done nothing if you want i will update my question with a screen shot with the capabilites tab @ChintaN-Maddy-Ramani — Mohan Gopi, May 15 '17 at 06:58
@MohanGopi under provisioning profile choose automatic. Do not choose profile and check. — ChintaN -Maddy- Ramani, May 15 '17 at 07:01
Check http://stackoverflow.com/questions/37806538/code-signing-is-required-for-product-type-application-in-sdk-ios-10-0-stic — ChintaN -Maddy- Ramani, May 15 '17 at 07:03
Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/144226/discussion-between-chintan-maddy-ramani-and-mohan-gopi). — ChintaN -Maddy- Ramani, May 15 '17 at 07:07

score 52 · Answer 1 · edited Jul 15 '19 at 19:10

52

I had the same problem in a project that i used push notifications what i did to fix it is : Target-> Capabillities and turned on push notifications .fix

Note: the answer from @codebrew explains this clever fix further.

edited Jul 15 '19 at 19:10

Fattie

27,874
70
431
719

answered Aug 31 '17 at 08:09

Alexis_Ni

907
7
14

2

I have no idea why this fixed it.. but it did. Many thanks. – Ash Nov 22 '17 at 19:31
it works for nativescript project also! you saved my night! Thanks – AsyncTask Feb 27 '18 at 22:25
lol 3 days wasted and this was the solution. How come Push Notifications got unticked in the first place I never know. – JanithaR Mar 21 '18 at 06:07
1

This worked for me too-- just turn push notifications on and back off. – Kip Apr 27 '18 at 20:22
This happened to me as well. For an older project that I was updating, I had forgotten to turn on GameCenter in the Capabilities tab. – Chris Livdahl May 01 '18 at 20:14
You save me to send to the trash a complete day! Tnks! – Anibal Itriago Jun 15 '18 at 15:33
awesome. It's problem with not synchronous entilements – James Nguyen Oct 30 '18 at 08:05
And this was the silver bullet. Thanks! – butter_baby Mar 26 '19 at 02:52
Woah! I could never think this will actually sole the problem. Thanks a ton. almost 3 days wasted. Thanks! – ankitjain11 Apr 04 '19 at 09:48

score 46 · Answer 2 · edited Mar 18 '19 at 15:33

46

I was able to resolve this by deleting all my provisional files on my computer (~/Library/MobileDevice/Provisioning Profiles) and restarting Xcode.

edited Mar 18 '19 at 15:33

Paul Cantrell

9,175
2
40
48

answered Sep 21 '17 at 17:10

Jim Bak

638
1
8
17

Ran into this on iTunes Connect. Deleted all my PP, restart Xcode, resolved. Oh and I believe this occurred because I added a new device in between Archive builds and then got this issue. Weird. – MichaelG Oct 20 '17 at 03:25
Thanks for sharing it – mastro35 Jan 25 '18 at 11:36

Luke Davis · Answer 3 · 2019-04-10T15:33:53.213

28

I was able to fix this same issue by turning on push notifications and then turning them back off.

Not sure why this works, but in Xcode 9.4.1, and Xcode 10 Beta this fix still works.

Update: This works in Xcode 10.1 & 10.2

edited Apr 10 '19 at 15:33

answered Aug 01 '18 at 18:25

Luke Davis

315
3
9

I had the same issue twice across two different projects, similar circumstances, and different Xcode versions. Worked both times. – Luke Davis Nov 13 '18 at 23:01
Worked. It creates .entitlements file so that's probably why. – Chuck Boris Apr 25 '19 at 16:32
Worked when encountering this issue when submitting an app through Xcode 10.3 (and 11.1). – Stunner Jan 13 '20 at 11:20
Still works with Xcode 11.3. This is embarrassing, Apple -_- – Ahmed Khalaf Jan 30 '20 at 12:57

score 16 · Answer 4 · answered Oct 04 '18 at 18:11

16

Xcode 9 and 10 may pop up this error because it's looking for a entitlements file for the target. You can turn on Push Notification in the target's Capabilities tab then turn it off to create an empty entitlements file for the build, then this error goes away.

answered Oct 04 '18 at 18:11

CodeBrew

6,457
2
43
48

2

THAT'S A REALLY CLEVER TIP ! – Fattie Dec 20 '18 at 21:12
1

Typical Apple bull crap. – GeneCode Feb 09 '19 at 10:34
You just saved my life ;) – Swissdude Jun 15 '19 at 23:35

score 7 · Answer 5 · answered May 15 '17 at 08:47

7

Under Code Signing Identity, change iPhone Distribution to iPhone Developer for Debug section.

answered May 15 '17 at 08:47

xiangxin

409
6
18

score 2 · Answer 6 · answered Mar 13 '19 at 09:26

I had this issue becaue XCode wasn't generating the entitlements file for Objective-C projects, no matter what I did. I solved it by doing the following:

Create an empty file at the root of your project(at $SRC_ROOT).
Paste the empty entitlements file template

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
</dict>
</plist>

Save it as YourAppName.entitlements
Go to Build Settings -> Signing -> Code Signing Entitlements and enter the path to your entitlements file - in my case $(SRCROOT)/YourAppName.entitlements

You might need to regenerate the Provisioning profiles after this (see @Jim Bak's answer above).

I tested many things but this was the only thing that worked for me. Thanks! — mxch, Mar 14 '19 at 12:01

score 2 · Answer 7 · edited Jun 20 '20 at 09:12

2

For 2020 ..

Incredibly, Apple still have not fixed this in Xcode 11 onwards ...

The usual fix is the @CodeBrew solution above:

"turn on Push Notification in the target's Capabilities tab then turn it off ... this error goes away.

It's that easy (usually).

edited Jun 20 '20 at 09:12

Community

1
1

answered May 13 '20 at 22:54

Fattie

27,874
70
431
719

score 1 · Answer 8 · answered Jun 02 '17 at 14:43

I'm very new to iPhone development too and had an identical issue with an ionic project. I executed ionic cordova platform add ios, navigated XCode to the ionic generated platforms/ios/, checked the bundle id, associated my Apple developer Id with this App, let XCode manage my signing certs and provisioning profiles and hit the problem immediately.

So I made an XCode generated project with the same Bundle identifier and Apple developer team values and that was all cool. Which proved my Apple Id and certs were fine.

I compared the Code Signing values under XCode Building Settings (All) and in my case the issue was around the contents of the debug version Code Signing Entitlements file, which revealed I hadn't set up the aps-environment stuff properly.

score 1 · Answer 9 · answered Oct 25 '17 at 14:43

1

For me unchecking and re-checking "Automatically manage signing" (on "General" tab) solved this.

answered Oct 25 '17 at 14:43

Chuck Boris

1,275
1
11
9

score 0 · Answer 10 · answered Aug 05 '18 at 05:41

I had the same issue on a multiplatform project (iOS / macOS). In my case the problem was caused because the Code Signing Entitlements build settings of both the iOS and macOS app referred to the same Entitlements.plist file that was part of the macOS app. So to fix this I created an empty Entitlements.plist for iOS and made the iOS build setting refer to this file.

score 0 · Answer 11 · answered Feb 20 '19 at 01:31

For me the answer was turning on and then off at least one thing in the Capabilities page for ALL targets. The app, watch and watch extension. Even though I already had entitlement files that exactly matched what xCode created, something else changed when it regenerated the files.

score 0 · Answer 12 · answered Jun 18 '19 at 02:23

I had the same problem with Xcode 10.2. I noticed the errors went away when I switched to the simulator device instead of my test devices. So I copied the source code of the entitlements file in case I needed to recreated it and deleted the contents of it. I ran build with my first test device physically connected. It made me type in my mac password about 40 times while it created the build but then it added the information back to the entitlements file and the errors went away. Turning notifications on and off didn't work and neither did adding capabilities to the developer account in any configuration.

score 0 · Answer 13 · answered Mar 18 '20 at 18:37

0

On Xcode 11, make sure to remove this line:

<key>BuildSystemType</key>
<string>Latest</string>

Seems like this was only necessary whe there was two distinct build types and now it just breaks the building.

answered Mar 18 '20 at 18:37

Dielson Sales

1,715
1
20
25

Automatic signing is unable to resolve an issue with the "projectName" target's entitlements file

13 Answers13

For 2020 ..

The usual fix is the @CodeBrew solution above:

Linked