Provisioning profile doesn't include the application-identifier and keychain-access-groups entitlements

Question

I've tried all the other questions and searched everything on this that I could already, a lot of the other questions involved existing apps that were being updated or people with developer accounts but this is like my second time using Xcode and it has worked before.

This just happened out of nowhere. I keep getting these two errors and it allows me to run simulators but not build onto my iPhone:

1. Automatic signing is unable to resolve an issue with the "LearningSpriteKit" target's entitlements. Automatic signing can't add the application-identifier and keychain-access-groups entitlements to your provisioning profile. Switch to manual signing and resolve the issue by downloading a matching provisioning profile from the developer website. Alternatively, to continue using automatic signing, remove these entitlements from your entitlements file and their associated functionality from your code.

2. Provisioning profile "iOS Team Provisioning Profile: #####.LearningSpriteKit" doesn't include the application-identifier and keychain-access-groups entitlements.

Solution 1

This issue is related to Bug 1534145. SSL.com: P-384 curve / ecdsa-with-SHA256 certificates.

A representative from Apple estimated 558,000 certificates to become invalidated: Bug 1533655. DigiCert: Apple: Non-compliant Serial Numbers

GoDaddy, Google, Apple and Facebook (that would explain why Facebook was glitchy today) are affected.

They are working on resolving the issue right now.

That would explain our problems, folks!

Update: The issue has been resolved. Try to refresh your projects.

Solution 2

Workaround: change Bundle Identifier and/or Version.

Solution 3

I restored a profile from Time Machine when this was working and upon launch, Xcode immediately deletes and replaces it with a new one. The key difference seems to be the old profile has the get-task-allow entitlement while the new one has NO entitlements. This is definitely broken at Apple's end.

Edit: The entitlements should also include a keychain access group, but again, no entitlements at all. Should look like:

Solution 4

EDIT

As per latest update Apple successfully resolved Automatically Code Sign with Free Account issue.

I tried it and I can confirm its resolved.

Please try at your end.

Update

Tested with Latest XCode 10.2 and it's working fine + they improved performance of overall Xcode & codesign feature.

I am also facing the same issue while I am creating a new Profile from Xcode and if I go to other projects and check over there also I am facing the same issue as below.

Due to this issue, none of my projects can build with the old profile and certificate.

The strange issue, so I checked a newly created Profile and compared with the old one, and I found that App ID is unknown as well as there were no Entitlement details in the newly created profile.

Check the below screenshots of the old and new profile comparison:

Old Profile:

New Profile:

So it means it's not able to set App Id and Entitlements in the new profile. So the end result does not work all old profiles and giving the same error in all projects.

Issue Workaround:

Step1: Go to Provisioning Profile folder (path: ~⁨Library⁩ ▸ ⁨MobileDevice⁩ ▸ ⁨Provisioning Profiles⁩).

Or use a shortcut to jump directly into this folder like CMD + Shift + G and enter ~/Library/MobileDevice/Provisioning Profiles it will redirect your finder directly on the Provisioning Profiles folder.

Step2: Sort the files inside that folder by Date Modified.

Step3: Check profile with Unknown App Id and delete all unknown profiles.

Step4: Come back on Xcode and check all old projects will work as expected.

Note: Make sure none of your project open while doing above changes. Otherwise, it will create a new profile with Unknown App Id.

I hope this will help and Apple will solve this bug soon!

Solution 5

It seems Apple broke the automatic signing system. I was playing around with a few projects and Xcode just fetches the incorrect profile.

This worked for me:

1. Turn off "Automatically manage signing" in project target
2. Go to ~/Library⁩/⁨MobileDevice⁩/⁨Provisioning Profiles⁩
3. Remove previously downloaded profiles
4. Turn on "Automatically manage signing" again

View more solutions

Comments

[yeralin]

Also experiencing this. Might be a global thing, asking other developers to confirm on ios-developers.slack.com

[Renan Aguiar]

Same here! Cant run on an iphone. only emulator

[冯剑龙]

Apple's server may be down because of all of us meet the same question.

[Tieda Wei]

Same here. Not a paid developer account.

[siva prasanna]

Yes I too think so, same problem with my free account

[Timur X.]

Can somebody confirm if this is a temporary issue?

[Susy Valentina Rahardjo]

same here. yesterday it is okay, but now after i change the bundle id, it give me this error

[Piyush]

yes, I am also facing same issue. I think it also an issue with free account

[CodeChanger]

I think its not server issue as i have checked status of Xcode Automatic Configuration and its in active state check status here developer.apple.com/system-status may be some other issue or glitch by apple.

[Dnyaneshwar Shinde]

Go to capabilities and enable keychain sharing.

[Bikshapathi Kumbala]

I got this problem today only for free apple developer account.

[Tanner H.]

Definitely still happening for me, this is the first time it's ever happened

[Jan]

Same problem. NOT a free account, but using the Personal Team

[byemute]

Same problem, Paid Account

[flo071]

It looks like the problem only occurs with personal teams, according to the comments in this thread. Is there a way to change from personal to any other team type? maybe this would help.

[Bilfred]

This seems to be occurring on any free developer accounts, and new projects on paid developer accounts. However, some people have also reported new developer account enrollment to be broken :/

[Bilfred]

@CodeChanger working as intended ;)

[David Gish]

I believe that is correct. Once my team added me, I selected the team in Xcode and build errors went away.

[L_Cleo]

There is actually a work-around, I mean it works for me. stackoverflow.com/questions/55146587/…

[Oscar]

Still broken. Apple forum is disgruntled too: forums.developer.apple.com/thread/114539

[Sam]

Same issue when attempting to sideload

[CodeChanger]

Issue resolved now try again with new identifire its resolved by Apple.

[Bikshapathi Kumbala]

There will be a workaround here for the above problem. stackoverflow.com/questions/55146587/…

[Amish]

Now it does not show up the Entitlements error. Instead it shows Build Succeeded but while launching the app on device, following error is thrown "iPhone has denied the launch request." This error is coming on every xcode project on every iOS device.

[Andrei Calazans]

@Amish check this out stackoverflow.com/questions/55159807/… . He uncheck Debug Executable checkbox and it works.

[Jack A]

I know people with paid developer accounts and it works for them.

[Adel Ahmadyan]

The issue seems to be fixed on Apple's end. As of 3/14.

[SinLok]

I encounter "iPhone has denied the launch request" error today. Is this related to this problem?

[Ali Beadle]

@SinLok, same here. It is unclear to me whether it is the same problem or whether part of the fix (deleting certificates in my case) is causing secondary issues. Turning off debug executable in the scheme is a workaround (not a good one, because you cannot then debug the device) for now. I guess we have to then wait to see what develops. I fear more messing around with certificates and settings may just break more things!

[Admin]

Any solution here yet? I am still getting this problem

[Qbyte]

Hello everyone, I've created a StackOverflow room to chat about the "iPhone has denied launch request" issue: chat.stackoverflow.com/rooms/190218/…

[Admin]

Free accounts seem to only have this problem

[Fedorov7890]

For me that does not work. Also I think you mean ~/Library⁩/⁨MobileDevice⁩/⁨Provisioning Profiles⁩

[Oleh Zayats]

@Fedorov7890 Yep, corrected. What message do you see?

[Fedorov7890]

Remark: looks like it works for projects created yesterday and earlier, but not for today's project

[Ali Beadle]

Interesting, but we have XCode 10.1 showing this problem and 10.1 does support SDK 12.

[Jake]

Okay sure thing, I've managed to get a temp workaround by cleaning the project in Xcode and only running in debug via my IDE (I'm using VSC) through a simulator.

[Ali Beadle]

As the OP said, simulators seem unaffected by the problem. It appears to only affect real devices.

[Franky]

Where is that ~Library path, please?

[Bilfred]

@Franky ~/Library⁩/⁨MobileDevice⁩/⁨Provisioning Profiles. Although this fix does not work for me (and others, as seen in other answers). Your mileage may vary.

[Jake]

Yeah I haven't been able to load on a physical device. Hope Apple fixes this soon.

[Franky]

@Bilfred My macOS X is Sierra 10.13.6 and there isn't such a path in ~Library!

[Jake]

Glad to hear Apple is dealing with this/has spoken out about the issue

[Tanner H.]

How long should this take? I'm looking to deploy my app to my watch as soon as I can.

[David Gish]

Invalidated certs don't explain why new ones Apple is issuing are missing the necessary entitlements.

[Bilfred]

@DavidGish from what I can gather from the report, they're actually not issuing any certificates at the moment. On 2019-03-7 they stopped issuance of TLS certs, unsure if or how that applies.

[Ahamed Abdul Rahman]

For me, its worked. I was building 'Integration App' for Appium.Thanks for the solution, Oleh Zayats.

[Chase Patterson]

Works here. If it doesn't, try disabling "Automatically manage signing," delete the offending provisioning profile, change Bundle Identifier, enable auto signing, then add your team.

[Franky]

Thank you, please note that, there is only one ..mobileprovision file in that folder and that file contains three sections: iOS TEAM PROVISIONING PROFILE, CERTIFICATES and PROVISION DEVICES. In the iOS TEAM PROVISIONING PROFILE there is a line with App Unknown ID: as in this image. Now should I delete the file?

[Fedorov7890]

Does not work. It gives no errors or warnings, but the app refuses to launch on the device, like described here stackoverflow.com/questions/45421179/…

[CodeChanger]

yes delete that file and one more thing try again apple resolved above mention issue.

[Fedorov7890]

Still can not install on the device. Even with new free appleid and certificate

[Husein Behboudi Rad]

Did you removed all certificates?

[Fedorov7890]

Yes I did, besides I purged ~/Library/MobileDevice/Provisioning\ Profiles and ~/Library/Developer/Xcode/DerivedData and restarted iPhone

[Fedorov7890]

Finally it works with this workaround stackoverflow.com/a/54990369/3824328

[CodeChanger]

Its clearly says that provided bundle identifier already created so you need to create new bundle id to resolve this issue.

[Ava]

This fixed the problem for me at first, but then it came back again a few minutes later

[Linus]

Are there any updates to this? I feel like this should have highest priority. Any new ideas for workarounds?

[Franky]

What to write for Bundle Identifier and Version, please? I'm self-employed developer working at my own office. I wrote two a string and a number respectively for them and the sign errors are vanished, but I think can't run my app using the iOS kit (on Qt Creator)!

[Franky]

Where to remove certificates? What path?

[Mr Heelis]

this is the biggest cluster fumble I've ever come across in my life... to deliberately destroy $80+ million worth of certificates over some pedantic nonsense is joke... I just hope this is a lie and they were actually hacked and shut the whole thing off

[Renan Aguiar]

for denied lunch if i remove the debugger option, i cant debug while using the device. only simulator

[Fedorov7890]

@RenanAguiar you don't need to remove debugger option, just change 'Executable' from the drop-down list to "ask on launch". See link in my post that shows how to do that in pictures.

[david]

@Fedorov7890 To get the app launching on the device, you need to disable the debug executable checkbox in the scheme as explained in this comment iPhone has denied the launch request. This work around works for me after removing my dev account, cleaning up ~/Library/MobileDevice/Provisioning Profiles and changing the bundle identifier.

[Fedorov7890]

@david Thank you, I've already found an alternative solution without disable debug executable, stackoverflow.com/a/55160300/3824328

[Renan Aguiar]

when i do that, same thing happens. i cant see the debugger icons like step and location. only on the simulator

[Fedorov7890]

It looks like debugger is not fully functional. I can get console output from device, but breakpoints don't work; neither do step over / step into commands

[Jack A]

Apple fixed it.

[Renan Aguiar]

it doesnt! i cant debug or use location on the device

[bezoadam]

Right now I am not getting this error but instead I am getting "iPhone has denied the launch request".. any ideas?

[FractalSpace]

I can confirm that the above answer worked for me. Specifically, the app is built, singed and downloaded to my iPhone. I am using free developer's account. (March 14, 2019)

[Qbyte]

@bezoadam I'm also having this problem. Unfortunately I have no fix but just a workaround: Edit Scheme... -> Run -> Info -> "disable" Debug executable. This means e.g. that you cannot use breakpoints. Hope this helps!

[FractalSpace]

I did have this “iPhone has denied the launch request” issue, which went away with the above "ask to launch" workaround, but it is still annoying.

[Franky]

Hi, thanks. How to go to "keychain App" please? What path?

[David Gish]

You've probably found it by now, but the Keychain Access app is in Applications->Utilities

[Fabio Felici]

By looking at the phone logs I see these messages when debug executable is selected: SpringBoard [bundleidentifier] Provision violated for watchdog process-exit: <FBSProcessResourceProvision: 0x2812ee680; allowance: <; FBSProcessResourceAllowance; type: realTime; timeValue: 5.0s>; violated: YES> SpringBoard Not terminating "bundleidentifier" for violated provision because: "process is being debugged"

[Renan Aguiar]

i still cant debug using iphone with those answers

[yeralin]

@bezoadam I also started getting "iPhone has denied the launch request" Idk what exactly helped, but I tried (1) restarting laptop, (2) restarting iphone, (3) deleting app from iphone and reinstalling it again, and then eventually error went away

[N. Der]

@karabara any luck finding on how to do it?

[Renan Aguiar]

now i get it: Unable to launch /private/var/containers/Bundle/Application/52553D96-4B6A-468‌​0-B77C-C04895B7759C/‌​dois.app

[Admin]

I continue to have this problem.. What do I do I have tried deleting world wide developer certificate and changing bundle identifier. Nothing is working

[Qbyte]

@FabioFelici Hello everyone, I've created a StackOverflow room to chat about the "iPhone has denied launch request" issue: chat.stackoverflow.com/rooms/190218/…

[Renan Aguiar]

i use the free account.. by following whatever people say, now i get a error about waiting 7 days..... im not going to pay for testing it on my device.

[ShadowLightz]

Thx a lot, this was the very first thing that worked for me

[Fedorov7890]

Did it solve the 'iPhone has denied the launch request' problem for you?

[Dani]

@Fedorov7890 it did for me and I assume for ShadowLightz

[Fedorov7890]

In the updated solution debugger is fully functional.

[Eray T]

This right here solved the issue that I was having for about 5 hours >.<

[Andrew Morris]

Thank you. Thank you. Thank you.

[Kevin]

This worked for me! macOS Big Sur has issues with the old Xcode

[Ossir]

Save my day. Thanks!

[AlphaWulf]

@AndrewMorris Honestly, randomly trying anything I could come up with until this worked. It didn't help that all of the other answers are pointing to provisioning profiles and certificates to really throw you off track.

[jamauss]

This worked for the issue I was having as well