Provisioning profile missing entitlement: com.apple.developer.icloud

There are multiple technologies under the iCloud banner, and the error your posted only shows the start of the entitlement name (com.apple.developer.icloud-) so it’s hard to know which one you’re shooting for. So, some questions:

• Do you have automatic code signing enabled? It can generally fix problems like this… automatically.
• Did you enable this via a capability in the Signing & Capabilities editor?
• If so, which one?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thanks for your answer.

I want to clarify the situation.

• i use automatic signing with Signing & Capabilities editor
• at the moment iCloud is disabled and not used

I have cleaned all derived data - no change. I have reinstalled Xcode - no change. I have delete the project and reloaded it from my git repository - no change.

I have loaded the project on my MacBook. - and it compiles without any problem.

I have no clue what difference between these to systems is.

Quinn is helping this, which is great. I am just curious if the com.apple.developer.icloud- is really com.apple.developer.icloud-container-identifiers. I am guessing that the provisioning profile on your machine, either your notebook or Mac Mini, is not up to date, which leads to the different behaviors. Maybe you can try the following:

• Be sure your developer account is correctly set up in Xcode Settings > Apple Accounts, and your Mac has the access Apple's developer portal.

• Uncheck the Automatically manage signing box, and check it back. This tells Xcode to refresh the provisioning profile.

If that doesn't help, try to remove the iCloud capability – You are not using any iCloud feature, and so don't really need the capability just yet.

If you do need the iCloud capability, check one of the services, and pick an iCloud container if the service you checked is iCloud Documents or CloudKit. This is how folks use the capability. If everything goes well, the .entitlements file in your project should have something like below (assuming the CloudKit servicie is used), and the provisioning profile should be Automatically updated:

<key>com.apple.developer.icloud-container-identifiers</key>
<array>
	<string>your.container.identifier</string>
</array>
<key>com.apple.developer.icloud-services</key>
<array>
	<string>CloudKit</string>
</array>

I am super curious if this helps.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

If that doesn't help, try to remove the iCloud capability

Yeah, that’s what I recommend you do first. As Ziqiao says, it’s all disabled, so removing it doesn’t cost you anything. And I think it’ll get your app building again. Once you’re back in that stable state, you can add it back in and let Xcode’s automatic code siging do its thing.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thank you for your replies. Unfortunately, this didn't help either.

I developed an app with SwiftDate in a GroupContainer. The data model is stable, and all relationships are optional. The next step should be to switch to an iCloudContainer.

Both computers are on the same network and have internet access and access to the developer account. I disabled and re-enabled automatic signing. No change.

A comparison of the project.pbxproj files showed two new lines in the non-functional project:

1. 913a913

CODE_SIGN_IDENTITY = "Apple Development";

1. 948a949

PROVISIONING_PROFILE_SPECIFIER = "";

I manually deleted these two lines and restarted Xcode. There was no change in behavior; the same error occurred. I also manually downloaded the profile from the developer website and tried to sign it manually. But this deployment profile has the same error again:

Entitlements: 8 included, 1 Missing

What surprises me is that the working version on the MacBook lists 12 entitlements. The entitlements are identical on both systems.

<key>aps-environment</key>
<string>development</string>
<key>com.apple.developer.aps-environment</key>
<string>development</string>
<key>com.apple.developer.group-session</key>
<true/>
<key>com.apple.developer.icloud-container-identifiers</key>
<array/>
<key>com.apple.developer.icloud-services</key>
<array/>
<key>com.apple.security.application-groups</key>
<array>
        <string>group.de.hjbrede.bredeseck</string>
</array>

I guess there is something wrong with the signatures. Because my Xcode about is about to expire in the next couple of days, I am thinking of canceling that subscription and than buy a new one with new ids.

My standard process for debugging problems like is:

1. Test with a new project, with a completely different App ID.
2. If that fails, something fundamental is wrong.
3. But if it works, test with another new project, but this time using the sample App ID as your original project.
4. If that fails, then the issue is tied to the code signing setup for that specific App ID.
5. But if it works then you know the issue like in the main project itself.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I was offline for a couple of days. I stepped through the above steps. Step one was working OK. Step 3 was working OK. I have no idea what is going wrong. I think I will revoke my developer certificate an try to start with a fresh one.

Xcode must store some information outside of of the source code with is GIT controlled.