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

Answer 1

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.

Answer 2

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.

Answer 3

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.

Answer 4

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.

Answer 5

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

Answer 6

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:

1. Create an empty file at the root of your project(at $SRC_ROOT).
2. 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>

3. Save it as YourAppName.entitlements
4. 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).