KexAri
KexAri

Reputation: 3977

Missing entitlements file

I'm suddenly getting two warnings in XCODE:

/Users/me/Documents/Misc IOS DEV/myAPP/myAPP.xcodeproj Missing entitlements file for target myAPPUITests: "/var/folders/wb/9dsv1b5j53n8qbwmbh49qf9m0000gn/T/Entitlements.plist-gmk"

/Users/me/Documents/Misc IOS DEV/myAPP/myAPP.xcodeproj Missing entitlements file for target myAPPUITests: "/var/folders/wb/9dsv1b5j53n8qbwmbh49qf9m0000gn/T/Entitlements.plist-pCm"

Anyone have any idea what these are and how I can remove the warnings? Thanks!

Upvotes: 11

Views: 30934

Answers (9)

Ahmad Labeeb
Ahmad Labeeb

Reputation: 1098

Ok go to your target build settings and go to signing section in code signing entitlements delete the path for entitlements

Upvotes: 40

Peter Schorn
Peter Schorn

Reputation: 987

If you've enabled "Automatically manage signing" for your target(s), then go to your target settings, choose the "Signing & Capabilities" tab, and uncheck and then re-check "Automatically manage signing". It worked for me.

Upvotes: 0

ZeroOne
ZeroOne

Reputation: 684

Go to Project> Target > Build Settings > Signing

Here in 'CODE_SIGN_ENTITLEMENTS', put your path.

$(SRCROOT)/ProjectName/PathToFolder/AnotherFolder/YourProject.entitlements

Upvotes: 2

Ansyar Hafid
Ansyar Hafid

Reputation: 279

Click on your Project Targets, select Capabilities tab, and look for an issue on one of the enabled item. Click on the fix button. Another way to do this also by going to the Build Settings, search for Code Signing Entitlements, make sure it shows "yourProjectModule/EntitlementName.entitlements"

Upvotes: 0

user707650
user707650

Reputation:

Depending on what you want, you can opt to not sign your software (for e.g. local builds, simply playing around).

Select your project in the tree view (item at the top), then in the main window, select "Build Settings", navigate to the section "Code Signing", which is where the error occurs ("code signing entitlements"). Then, for "Code Signing Entity", simply select "Don't Code Sign".

Just remember to update this when you do need to sign your app.

Upvotes: 0

Gabe12
Gabe12

Reputation: 627

Product > Clean has worked for me multiple times.

Upvotes: 3

Jordan Smith
Jordan Smith

Reputation: 10378

Restarting Xcode fixed the issue for me.

The folder those warnings reference is a per-user temporary file/folder cache. If restarting Xcode doesn't fix the issue, I'd suggest restarting OSX.

Upvotes: 10

AWebster
AWebster

Reputation: 141

By assigning your Apple Developer ID to the Code Signing Identity section of the Build settings, this should clear up the warning messages.

Upvotes: 2

Al.
Al.

Reputation: 301

In case anyone finds this, the same happened to me with a new OSX project in the XCode 7.2.

In my case, I needed to add my device to my Developer account at https://developer.apple.com, and also create Provisioning Profile for the app.

I added my device by hand using the UUID from the 'Identifier' value in XCode's Devices Window.

I let XCode create the Provisioning Profile, by using the Organizer Window, selecting my App, and then clicking the 'Export ...' button and choosing 'Export a Development-signed Application'.

That cleared up the errors on the next build.

Upvotes: 0

Related Questions