Provisioning profile doesn't include the appli

2020-06-23 06:37发布

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.

标签: ios xcode
15条回答
女痞
2楼-- · 2020-06-23 07:09

This issue has been resolved, BUT some people still have a problem with it. If you're one of them, try the following:

1. In the General tab of target settings - uncheck the Automatically manage signing option

2. Close Xcode (fully, not just your project)

3. Erase .mobileprovision files under ~/Library/MobileDevice/Provisioning Profiles/

4. In Keychain Access, delete the following:

  • iPhone Developer: youremail@email.com
  • Developer ID Certification Authority
  • Apple Worldwide Developer Relations Certification Authority 3.

5. Delete the app on your iOS devices

6. Restart your Mac and iOS devices

7. Open Xcode again

8. Change the Bundle Identifier (even if it's a single character, you'd change it back to the original after you get it going)

9. Check the Automatically manage signing option

10. Use USB to connect your iPhone/iPad.

11. Make sure you trust your certificate on your iOS devices

This should do work for you.

查看更多
兄弟一词,经得起流年.
3楼-- · 2020-06-23 07:11

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.

Enter image description here

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:

Enter image description here

New Profile:

Enter image description here

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!

查看更多
走好不送
4楼-- · 2020-06-23 07:11

I got it to work by doing the following steps:

  1. Go to Xcode
  2. Preferences
  3. Accounts
  4. Manage certificates
  5. Plus sign
  6. iOS Development
  7. Done
  8. Download manual Profiles
  9. Close
  10. Go to your target
  11. Change development team to none
  12. Change development team to your previous team

It should work.

查看更多
爷的心禁止访问
5楼-- · 2020-06-23 07:13

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.

查看更多
可以哭但决不认输i
6楼-- · 2020-06-23 07:14

Maybe forum post [iOS 12 SDK] - deadline March 2019 - Legacy Mode might help.

It talks about Apple refusing to build iOS applications under SDK 12 as of March 2019 (OP from Dec 2018).

I've not yet tried this, but it may be linked to the issue. I have a free developer account and am also experiencing this bug.

Here's a screenshot in case the link changes (screenshot 1 below).

This is the link from the first screenshot (screenshot 2 below)

1sdk_12_issue

2iphone_xs_max_support_image

查看更多
聊天终结者
7楼-- · 2020-06-23 07:16

Here is the solution:

  1. Let Xcode be open.

  2. Select your developer account and let the error appear again.

  3. Go to the keychain app

4.a) Goto certificate section

4.b) Remove All (valid and invalids) certificates (I have three valid and many invalid!)

Remove certificates

  1. After removing the last certificate, macOS will recreate a new certificate for the active developer account automatically.

  2. Run your app in your iDevice. You need to enter your system password to add newly created certificate into the Keychain.

If in the second run it says

Your iPhone has denied the launch request

Just go to:

ProductScheme → *edit scheme: uncheck "Debug executable"

I hope it solves your problem.

查看更多
登录 后发表回答