Provisioning profile doesn't include the appli

Question

This post relates to a rapidly changing event.

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.

Answer 1

Here is a temporary workaround:

1. Change Bundle Identifier: Target → General → Identity → Bundle Identifier (set this to a different value than it is right now)
2. Change Version: Target → General → Identity → Version
3. Disable debug executable: Product → Scheme → Edit Scheme (uncheck the box that says "debug executable")
4. Delete Provisioning Profiles: ~/Library/MobileDevice/Provisioning Profiles delete everything in this folder.

You now should be able to build and run projects on simulators and devices.

Answer 2

Workaround: change Bundle Identifier and/or Version.

Answer 3

I am finally able to deploy to our iOS devices again. Here are the steps I took to make it work.

First, I followed all 10 steps in Zameer's answer here. I have copied them below:

1. Open your project in XCode.
2. Select your project from the project navigator and then select your target from the column.
3. Click on the General tab and under the Signing section, make sure "Automatically manage signing" is enabled.
4. Click on the Capabilities tab and turn On both the "App Groups" and "Keychain Sharing" settings. This might raise an "Automatic signing failed" popup error, just click cancel to make it go away.
5. This should generate a entitlements file for you named nameProject.entitlements in the project folder of your project navigator.
6. Move this entitlements file outside of the folder, just below your project file.
7. Select your target again and return to the Capabilities tab to turn Off both the "App Groups" and "Keychain Sharing" settings. This again might raise an "Automatic signing failed" popup error, just click cancel to make it go away.
8. Now select your project above the target and go to Building Settings tab.
9. Scroll down to the Code Signing Identity setting under the Signing header and select iOS Developer from each drop down.
10. Under the above Signing header, double click the text field beside the Code Signing Entitlements and enter the name of your entitlements file, nameProject.entitlements.

After completing those 10 steps, the 2 red entitlement error messages in XCode went away and I was able to build and deploy the XCode test app to the iPhone and run it.

Although that XCode test app could build and deploy, I develop on a PC using Xamarin and I was unable to deploy my Xamarin.iOS application to my iOS devices and kept getting an error in Visual Studio: the executable was signed with invalid entitlements. I did the following things and now I can deploy my Xamarin app and run it on my iOS devices:

1. I deleted the provisioning profile from the Mac in the ~/Library/MobileDevice/Provisioning Profiles directory. XCode immediately generated a new provisioining profile (I'm not sure if this step was necessary but I'm just writing it because that's what I did).
2. I changed my Xamarin.iOS.csproj file and removed Entitlements.plist from the CodesignEntitlements element so it now just looks like <CodesignEntitlements></CodesignEntitlements>. Visual Studio automatically added two elements to the same propertygroup in the project which are probably not necessary but I thought I'd mention: <CodesignExtraArgs /> and <CodesignResourceRules />.