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












68















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's 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: BShoffner.LearningSpriteKit" doesn't include the application-identifier and keychain-access-groups entitlements.











share|improve this question









New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










Post is related to a rapidly changing event.










  • 2





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

    – yeralin
    13 hours ago






  • 3





    Same here! Cant run on an iphone. only emulator

    – Renan Aguiar
    12 hours ago






  • 2





    Same here. Not a paid developer account.

    – T. Wei
    10 hours ago






  • 2





    Facing the same problem with a free account

    – Devendra Bahirat
    7 hours ago






  • 2





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

    – Piyush
    6 hours ago
















68















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's 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: BShoffner.LearningSpriteKit" doesn't include the application-identifier and keychain-access-groups entitlements.











share|improve this question









New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










Post is related to a rapidly changing event.










  • 2





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

    – yeralin
    13 hours ago






  • 3





    Same here! Cant run on an iphone. only emulator

    – Renan Aguiar
    12 hours ago






  • 2





    Same here. Not a paid developer account.

    – T. Wei
    10 hours ago






  • 2





    Facing the same problem with a free account

    – Devendra Bahirat
    7 hours ago






  • 2





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

    – Piyush
    6 hours ago














68












68








68


45






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's 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: BShoffner.LearningSpriteKit" doesn't include the application-identifier and keychain-access-groups entitlements.











share|improve this question









New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












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's 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: BShoffner.LearningSpriteKit" doesn't include the application-identifier and keychain-access-groups entitlements.








ios xcode






share|improve this question









New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 15 hours ago









rmaddy

244k27324386




244k27324386






New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 16 hours ago









Jack AJack A

30134




30134




New contributor




Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Jack A is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



Post is related to a rapidly changing event.




Post is related to a rapidly changing event.









  • 2





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

    – yeralin
    13 hours ago






  • 3





    Same here! Cant run on an iphone. only emulator

    – Renan Aguiar
    12 hours ago






  • 2





    Same here. Not a paid developer account.

    – T. Wei
    10 hours ago






  • 2





    Facing the same problem with a free account

    – Devendra Bahirat
    7 hours ago






  • 2





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

    – Piyush
    6 hours ago














  • 2





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

    – yeralin
    13 hours ago






  • 3





    Same here! Cant run on an iphone. only emulator

    – Renan Aguiar
    12 hours ago






  • 2





    Same here. Not a paid developer account.

    – T. Wei
    10 hours ago






  • 2





    Facing the same problem with a free account

    – Devendra Bahirat
    7 hours ago






  • 2





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

    – Piyush
    6 hours ago








2




2





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

– yeralin
13 hours ago





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

– yeralin
13 hours ago




3




3





Same here! Cant run on an iphone. only emulator

– Renan Aguiar
12 hours ago





Same here! Cant run on an iphone. only emulator

– Renan Aguiar
12 hours ago




2




2





Same here. Not a paid developer account.

– T. Wei
10 hours ago





Same here. Not a paid developer account.

– T. Wei
10 hours ago




2




2





Facing the same problem with a free account

– Devendra Bahirat
7 hours ago





Facing the same problem with a free account

– Devendra Bahirat
7 hours ago




2




2





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

– Piyush
6 hours ago





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

– Piyush
6 hours ago












6 Answers
6






active

oldest

votes


















18














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






share|improve this answer



















  • 2





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

    – siva prasanna
    9 hours ago








  • 1





    Can somebody confirm if this is a temporary issue?

    – Timur X.
    9 hours ago






  • 2





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

    – Susy Valentina Rahardjo
    7 hours ago






  • 2





    same here, free account

    – tunggad
    7 hours ago






  • 5





    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.

    – CodeChanger
    6 hours ago



















8














The Errors that I've got:




  • Showing Recent Messages :-1: Provisioning profile "iOS Team
    Provisioning Profile: HealthCenter.HealthCenter" doesn't support the
    HomeKit and Keychain Sharing capability. (in target 'HealthCenter')

  • Showing Recent Messages :-1: Provisioning profile "iOS Team
    Provisioning Profile: HealthCenter.HealthCenter" doesn't include the
    com.apple.developer.homekit and keychain-access-groups entitlements.
    (in target 'HealthCenter')

  • Automatic signing failed Xcode failed to provision this target.
    Please file a bug report at https://bugreport.apple.com/ and
    include the Update Signing report from the Report navigator.


I tried everything that I can,




  1. changed bundle identifier (add random numbers to the end .. )

  2. clean build folder,close & reopen

  3. enabled keychain sharing (Project->Targets->Capabilities->Keychain Sharing)

  4. unchecked automatically manage signing (Project->Targets->General->Signing)

  5. change my apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account)

  6. add certificate to the apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account -> Apple IDs -> Manual Certificates...-> Add IOS Development )

  7. update Xcode

  8. update Mac

  9. Change Deployment Target to your device's release
    (Project->Targets->General->Deployment Info -> Deployment Target)

  10. Change Code Signing Identitiy to IOS Developer (Project -> Target -> Build Settings -> Signing -> Code Signing Identity -> Change all debug and release to IOS Developer)

  11. Change your destination (Xcode -> Product -> Destination -> Device -> Select your device)


...



But it seems that everybody has the same problem with free Apple ID developers since yesterday.. In my opinion, this is a bug in Apple Servers.. So, just report and wait :(



report here : https://bugreport.apple.com/




Note: You can work with the simulator until this problem is solved.




Good Luck,



G.






share|improve this answer


























  • are you creating new profile or getting issue in old profile ?

    – CodeChanger
    4 hours ago











  • I get the same error on both my profiles.

    – GUL EDA AYDEMİR
    3 hours ago











  • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

    – David
    2 hours ago



















2














I am also facing same issue while I am creating new Profile from XCode and if I go to other projects and check over there also I am facing same issue like below.



enter image description here



Due to this issue none of my project able to build with old profile & certificate.



Strange issue so I checked newly created Profile and compare with old one and I found that App ID is unknown as well as there is no Entitlement details in newly created profile.



Check below screen shots of Old and New profile comparison:



Old Profile:



enter image description here



New Profile:



enter image description here



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



Temporary Workaround:



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



Step2: Short folder by Date Modified.



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



Step4: Come back on XCode and check all old project will work as expected.




Note: Make sure new app which causing this problem keep that project
closed otherwise it will create new profile with Unknown App Id.




Hope this will helps and apple will solve this bug soon!






share|improve this answer

































    1














    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.






    share|improve this answer































      0














      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






      share|improve this answer



















      • 6





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

        – Fedorov7890
        3 hours ago





















      -1














      Go to capabilities and enable keychain sharing.






      share|improve this answer



















      • 4





        Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

        – Captain Newt
        5 hours ago






      • 1





        What does this mean? The answer is not providing enough information and seems like it is not related to the question.

        – Boris Nikolić
        1 hour ago











      • Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

        – Alirezak
        8 mins ago










      protected by Bhargav Rao 10 hours ago



      Thank you for your interest in this question.
      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



      Would you like to answer one of these unanswered questions instead?














      6 Answers
      6






      active

      oldest

      votes








      6 Answers
      6






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      18














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






      share|improve this answer



















      • 2





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

        – siva prasanna
        9 hours ago








      • 1





        Can somebody confirm if this is a temporary issue?

        – Timur X.
        9 hours ago






      • 2





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

        – Susy Valentina Rahardjo
        7 hours ago






      • 2





        same here, free account

        – tunggad
        7 hours ago






      • 5





        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.

        – CodeChanger
        6 hours ago
















      18














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






      share|improve this answer



















      • 2





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

        – siva prasanna
        9 hours ago








      • 1





        Can somebody confirm if this is a temporary issue?

        – Timur X.
        9 hours ago






      • 2





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

        – Susy Valentina Rahardjo
        7 hours ago






      • 2





        same here, free account

        – tunggad
        7 hours ago






      • 5





        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.

        – CodeChanger
        6 hours ago














      18












      18








      18







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






      share|improve this answer













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







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered 12 hours ago









      冯剑龙冯剑龙

      334210




      334210








      • 2





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

        – siva prasanna
        9 hours ago








      • 1





        Can somebody confirm if this is a temporary issue?

        – Timur X.
        9 hours ago






      • 2





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

        – Susy Valentina Rahardjo
        7 hours ago






      • 2





        same here, free account

        – tunggad
        7 hours ago






      • 5





        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.

        – CodeChanger
        6 hours ago














      • 2





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

        – siva prasanna
        9 hours ago








      • 1





        Can somebody confirm if this is a temporary issue?

        – Timur X.
        9 hours ago






      • 2





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

        – Susy Valentina Rahardjo
        7 hours ago






      • 2





        same here, free account

        – tunggad
        7 hours ago






      • 5





        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.

        – CodeChanger
        6 hours ago








      2




      2





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

      – siva prasanna
      9 hours ago







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

      – siva prasanna
      9 hours ago






      1




      1





      Can somebody confirm if this is a temporary issue?

      – Timur X.
      9 hours ago





      Can somebody confirm if this is a temporary issue?

      – Timur X.
      9 hours ago




      2




      2





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

      – Susy Valentina Rahardjo
      7 hours ago





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

      – Susy Valentina Rahardjo
      7 hours ago




      2




      2





      same here, free account

      – tunggad
      7 hours ago





      same here, free account

      – tunggad
      7 hours ago




      5




      5





      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.

      – CodeChanger
      6 hours ago





      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.

      – CodeChanger
      6 hours ago













      8














      The Errors that I've got:




      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't support the
        HomeKit and Keychain Sharing capability. (in target 'HealthCenter')

      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't include the
        com.apple.developer.homekit and keychain-access-groups entitlements.
        (in target 'HealthCenter')

      • Automatic signing failed Xcode failed to provision this target.
        Please file a bug report at https://bugreport.apple.com/ and
        include the Update Signing report from the Report navigator.


      I tried everything that I can,




      1. changed bundle identifier (add random numbers to the end .. )

      2. clean build folder,close & reopen

      3. enabled keychain sharing (Project->Targets->Capabilities->Keychain Sharing)

      4. unchecked automatically manage signing (Project->Targets->General->Signing)

      5. change my apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account)

      6. add certificate to the apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account -> Apple IDs -> Manual Certificates...-> Add IOS Development )

      7. update Xcode

      8. update Mac

      9. Change Deployment Target to your device's release
        (Project->Targets->General->Deployment Info -> Deployment Target)

      10. Change Code Signing Identitiy to IOS Developer (Project -> Target -> Build Settings -> Signing -> Code Signing Identity -> Change all debug and release to IOS Developer)

      11. Change your destination (Xcode -> Product -> Destination -> Device -> Select your device)


      ...



      But it seems that everybody has the same problem with free Apple ID developers since yesterday.. In my opinion, this is a bug in Apple Servers.. So, just report and wait :(



      report here : https://bugreport.apple.com/




      Note: You can work with the simulator until this problem is solved.




      Good Luck,



      G.






      share|improve this answer


























      • are you creating new profile or getting issue in old profile ?

        – CodeChanger
        4 hours ago











      • I get the same error on both my profiles.

        – GUL EDA AYDEMİR
        3 hours ago











      • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

        – David
        2 hours ago
















      8














      The Errors that I've got:




      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't support the
        HomeKit and Keychain Sharing capability. (in target 'HealthCenter')

      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't include the
        com.apple.developer.homekit and keychain-access-groups entitlements.
        (in target 'HealthCenter')

      • Automatic signing failed Xcode failed to provision this target.
        Please file a bug report at https://bugreport.apple.com/ and
        include the Update Signing report from the Report navigator.


      I tried everything that I can,




      1. changed bundle identifier (add random numbers to the end .. )

      2. clean build folder,close & reopen

      3. enabled keychain sharing (Project->Targets->Capabilities->Keychain Sharing)

      4. unchecked automatically manage signing (Project->Targets->General->Signing)

      5. change my apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account)

      6. add certificate to the apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account -> Apple IDs -> Manual Certificates...-> Add IOS Development )

      7. update Xcode

      8. update Mac

      9. Change Deployment Target to your device's release
        (Project->Targets->General->Deployment Info -> Deployment Target)

      10. Change Code Signing Identitiy to IOS Developer (Project -> Target -> Build Settings -> Signing -> Code Signing Identity -> Change all debug and release to IOS Developer)

      11. Change your destination (Xcode -> Product -> Destination -> Device -> Select your device)


      ...



      But it seems that everybody has the same problem with free Apple ID developers since yesterday.. In my opinion, this is a bug in Apple Servers.. So, just report and wait :(



      report here : https://bugreport.apple.com/




      Note: You can work with the simulator until this problem is solved.




      Good Luck,



      G.






      share|improve this answer


























      • are you creating new profile or getting issue in old profile ?

        – CodeChanger
        4 hours ago











      • I get the same error on both my profiles.

        – GUL EDA AYDEMİR
        3 hours ago











      • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

        – David
        2 hours ago














      8












      8








      8







      The Errors that I've got:




      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't support the
        HomeKit and Keychain Sharing capability. (in target 'HealthCenter')

      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't include the
        com.apple.developer.homekit and keychain-access-groups entitlements.
        (in target 'HealthCenter')

      • Automatic signing failed Xcode failed to provision this target.
        Please file a bug report at https://bugreport.apple.com/ and
        include the Update Signing report from the Report navigator.


      I tried everything that I can,




      1. changed bundle identifier (add random numbers to the end .. )

      2. clean build folder,close & reopen

      3. enabled keychain sharing (Project->Targets->Capabilities->Keychain Sharing)

      4. unchecked automatically manage signing (Project->Targets->General->Signing)

      5. change my apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account)

      6. add certificate to the apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account -> Apple IDs -> Manual Certificates...-> Add IOS Development )

      7. update Xcode

      8. update Mac

      9. Change Deployment Target to your device's release
        (Project->Targets->General->Deployment Info -> Deployment Target)

      10. Change Code Signing Identitiy to IOS Developer (Project -> Target -> Build Settings -> Signing -> Code Signing Identity -> Change all debug and release to IOS Developer)

      11. Change your destination (Xcode -> Product -> Destination -> Device -> Select your device)


      ...



      But it seems that everybody has the same problem with free Apple ID developers since yesterday.. In my opinion, this is a bug in Apple Servers.. So, just report and wait :(



      report here : https://bugreport.apple.com/




      Note: You can work with the simulator until this problem is solved.




      Good Luck,



      G.






      share|improve this answer















      The Errors that I've got:




      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't support the
        HomeKit and Keychain Sharing capability. (in target 'HealthCenter')

      • Showing Recent Messages :-1: Provisioning profile "iOS Team
        Provisioning Profile: HealthCenter.HealthCenter" doesn't include the
        com.apple.developer.homekit and keychain-access-groups entitlements.
        (in target 'HealthCenter')

      • Automatic signing failed Xcode failed to provision this target.
        Please file a bug report at https://bugreport.apple.com/ and
        include the Update Signing report from the Report navigator.


      I tried everything that I can,




      1. changed bundle identifier (add random numbers to the end .. )

      2. clean build folder,close & reopen

      3. enabled keychain sharing (Project->Targets->Capabilities->Keychain Sharing)

      4. unchecked automatically manage signing (Project->Targets->General->Signing)

      5. change my apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account)

      6. add certificate to the apple ID (Project->Targets->General->Signing-> Checked Automatically Manage Signing -> Team -> Dropdown to Add Account -> Apple IDs -> Manual Certificates...-> Add IOS Development )

      7. update Xcode

      8. update Mac

      9. Change Deployment Target to your device's release
        (Project->Targets->General->Deployment Info -> Deployment Target)

      10. Change Code Signing Identitiy to IOS Developer (Project -> Target -> Build Settings -> Signing -> Code Signing Identity -> Change all debug and release to IOS Developer)

      11. Change your destination (Xcode -> Product -> Destination -> Device -> Select your device)


      ...



      But it seems that everybody has the same problem with free Apple ID developers since yesterday.. In my opinion, this is a bug in Apple Servers.. So, just report and wait :(



      report here : https://bugreport.apple.com/




      Note: You can work with the simulator until this problem is solved.




      Good Luck,



      G.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited 4 hours ago

























      answered 4 hours ago









      GUL EDA AYDEMİRGUL EDA AYDEMİR

      994




      994













      • are you creating new profile or getting issue in old profile ?

        – CodeChanger
        4 hours ago











      • I get the same error on both my profiles.

        – GUL EDA AYDEMİR
        3 hours ago











      • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

        – David
        2 hours ago



















      • are you creating new profile or getting issue in old profile ?

        – CodeChanger
        4 hours ago











      • I get the same error on both my profiles.

        – GUL EDA AYDEMİR
        3 hours ago











      • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

        – David
        2 hours ago

















      are you creating new profile or getting issue in old profile ?

      – CodeChanger
      4 hours ago





      are you creating new profile or getting issue in old profile ?

      – CodeChanger
      4 hours ago













      I get the same error on both my profiles.

      – GUL EDA AYDEMİR
      3 hours ago





      I get the same error on both my profiles.

      – GUL EDA AYDEMİR
      3 hours ago













      This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

      – David
      2 hours ago





      This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

      – David
      2 hours ago











      2














      I am also facing same issue while I am creating new Profile from XCode and if I go to other projects and check over there also I am facing same issue like below.



      enter image description here



      Due to this issue none of my project able to build with old profile & certificate.



      Strange issue so I checked newly created Profile and compare with old one and I found that App ID is unknown as well as there is no Entitlement details in newly created profile.



      Check below screen shots of Old and New profile comparison:



      Old Profile:



      enter image description here



      New Profile:



      enter image description here



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



      Temporary Workaround:



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



      Step2: Short folder by Date Modified.



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



      Step4: Come back on XCode and check all old project will work as expected.




      Note: Make sure new app which causing this problem keep that project
      closed otherwise it will create new profile with Unknown App Id.




      Hope this will helps and apple will solve this bug soon!






      share|improve this answer






























        2














        I am also facing same issue while I am creating new Profile from XCode and if I go to other projects and check over there also I am facing same issue like below.



        enter image description here



        Due to this issue none of my project able to build with old profile & certificate.



        Strange issue so I checked newly created Profile and compare with old one and I found that App ID is unknown as well as there is no Entitlement details in newly created profile.



        Check below screen shots of Old and New profile comparison:



        Old Profile:



        enter image description here



        New Profile:



        enter image description here



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



        Temporary Workaround:



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



        Step2: Short folder by Date Modified.



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



        Step4: Come back on XCode and check all old project will work as expected.




        Note: Make sure new app which causing this problem keep that project
        closed otherwise it will create new profile with Unknown App Id.




        Hope this will helps and apple will solve this bug soon!






        share|improve this answer




























          2












          2








          2







          I am also facing same issue while I am creating new Profile from XCode and if I go to other projects and check over there also I am facing same issue like below.



          enter image description here



          Due to this issue none of my project able to build with old profile & certificate.



          Strange issue so I checked newly created Profile and compare with old one and I found that App ID is unknown as well as there is no Entitlement details in newly created profile.



          Check below screen shots of Old and New profile comparison:



          Old Profile:



          enter image description here



          New Profile:



          enter image description here



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



          Temporary Workaround:



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



          Step2: Short folder by Date Modified.



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



          Step4: Come back on XCode and check all old project will work as expected.




          Note: Make sure new app which causing this problem keep that project
          closed otherwise it will create new profile with Unknown App Id.




          Hope this will helps and apple will solve this bug soon!






          share|improve this answer















          I am also facing same issue while I am creating new Profile from XCode and if I go to other projects and check over there also I am facing same issue like below.



          enter image description here



          Due to this issue none of my project able to build with old profile & certificate.



          Strange issue so I checked newly created Profile and compare with old one and I found that App ID is unknown as well as there is no Entitlement details in newly created profile.



          Check below screen shots of Old and New profile comparison:



          Old Profile:



          enter image description here



          New Profile:



          enter image description here



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



          Temporary Workaround:



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



          Step2: Short folder by Date Modified.



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



          Step4: Come back on XCode and check all old project will work as expected.




          Note: Make sure new app which causing this problem keep that project
          closed otherwise it will create new profile with Unknown App Id.




          Hope this will helps and apple will solve this bug soon!







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 5 hours ago

























          answered 5 hours ago









          CodeChangerCodeChanger

          3,74211742




          3,74211742























              1














              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.






              share|improve this answer




























                1














                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.






                share|improve this answer


























                  1












                  1








                  1







                  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.






                  share|improve this answer













                  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.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 14 mins ago









                  David GishDavid Gish

                  440311




                  440311























                      0














                      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






                      share|improve this answer



















                      • 6





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

                        – Fedorov7890
                        3 hours ago


















                      0














                      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






                      share|improve this answer



















                      • 6





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

                        – Fedorov7890
                        3 hours ago
















                      0












                      0








                      0







                      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






                      share|improve this answer













                      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







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered 4 hours ago









                      Oleh ZayatsOleh Zayats

                      1,68311021




                      1,68311021








                      • 6





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

                        – Fedorov7890
                        3 hours ago
















                      • 6





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

                        – Fedorov7890
                        3 hours ago










                      6




                      6





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

                      – Fedorov7890
                      3 hours ago







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

                      – Fedorov7890
                      3 hours ago













                      -1














                      Go to capabilities and enable keychain sharing.






                      share|improve this answer



















                      • 4





                        Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

                        – Captain Newt
                        5 hours ago






                      • 1





                        What does this mean? The answer is not providing enough information and seems like it is not related to the question.

                        – Boris Nikolić
                        1 hour ago











                      • Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

                        – Alirezak
                        8 mins ago
















                      -1














                      Go to capabilities and enable keychain sharing.






                      share|improve this answer



















                      • 4





                        Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

                        – Captain Newt
                        5 hours ago






                      • 1





                        What does this mean? The answer is not providing enough information and seems like it is not related to the question.

                        – Boris Nikolić
                        1 hour ago











                      • Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

                        – Alirezak
                        8 mins ago














                      -1












                      -1








                      -1







                      Go to capabilities and enable keychain sharing.






                      share|improve this answer













                      Go to capabilities and enable keychain sharing.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered 5 hours ago









                      Dnyaneshwar ShindeDnyaneshwar Shinde

                      8913




                      8913








                      • 4





                        Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

                        – Captain Newt
                        5 hours ago






                      • 1





                        What does this mean? The answer is not providing enough information and seems like it is not related to the question.

                        – Boris Nikolić
                        1 hour ago











                      • Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

                        – Alirezak
                        8 mins ago














                      • 4





                        Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

                        – Captain Newt
                        5 hours ago






                      • 1





                        What does this mean? The answer is not providing enough information and seems like it is not related to the question.

                        – Boris Nikolić
                        1 hour ago











                      • Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

                        – Alirezak
                        8 mins ago








                      4




                      4





                      Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

                      – Captain Newt
                      5 hours ago





                      Xcode failed to provision this target. Please file a bug report at <bugreport.apple.com> and include the Update Signing report from the Report navigator.

                      – Captain Newt
                      5 hours ago




                      1




                      1





                      What does this mean? The answer is not providing enough information and seems like it is not related to the question.

                      – Boris Nikolić
                      1 hour ago





                      What does this mean? The answer is not providing enough information and seems like it is not related to the question.

                      – Boris Nikolić
                      1 hour ago













                      Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

                      – Alirezak
                      8 mins ago





                      Key sharing in Capabilities are a feature for the app. It doesn't relevant to this question

                      – Alirezak
                      8 mins ago





                      protected by Bhargav Rao 10 hours ago



                      Thank you for your interest in this question.
                      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                      Would you like to answer one of these unanswered questions instead?



                      Popular posts from this blog

                      Callistus I

                      Tabula Rosettana

                      How to label and detect the document text images