10

I am trying to fix this issue for hours now. I have checked the App ID and confirmed the iCloud containers. Also i have entered the same in the app entitlements.

But there is a always a red mark before "Add the “iCloud containers” entitlement to your App ID". I created the new provisioning profile and removed the expired provision files also. This is the first time i am facing this issue.

Is this issue related with the developer certificate signing or something?

enter image description here

Danboz
  • 541
  • 1
  • 4
  • 14

9 Answers9

12

I was having the same problem couple of days ago. Fixed it by doing these steps:

  1. Go to your developer account
  2. Find the App ID you are working on
  3. Click edit.
  4. On the iCloud section select the radio button that says "Include CloudKit support (requires Xcode 6)" enter image description here

Worked for me.

Community
  • 1
  • 1
Ashik
  • 1,123
  • 10
  • 21
4

For me everything was just fine. I had to close and reopen xcode. Then go to 'Capabilities' and Toggle the 'iCloud' i.e OFF and Then ON it again.

Idrees Khan
  • 7,404
  • 17
  • 59
  • 110
4

I solved this by:

  1. Turn off iCloud capabilities.

  2. Change the app's bundle id.

  3. Turn on iCloud capabilities.

Now everything is regenerated afresh, and the error goes away. Of course, now the bundle id is wrong. But now you can go to the member center, delete the old (faulty) app id and any associated provisioning profiles, and change the bundle id back again.

matt
  • 447,615
  • 74
  • 748
  • 977
  • 1
    I've found out why this works. It sets PRODUCT_BUNDLE_IDENTIFIER in the project.pbxproj file. – oferei Feb 11 '19 at 15:15
  • @oferei Fascinating and helpful if true! Thank you very much for your work on this. – matt Feb 11 '19 at 15:18
2

I was trying to add an App ID matching my project's bundle ID, but it still doesn't update the warnings in iCloud.

Then I found that in "General" -> "Signing" it says Target is ad hoc signed, and I tapped the Enable Development Signing button, then Xcode started to auto manage the App ID etc and everything turned green :]

hyouuu
  • 2,184
  • 1
  • 24
  • 34
  • Worked for me too, except in Xcode 9 the checkmarks are gray, not green, and originally it said `Target is unsigned`, because I've been signing by scripting the `codesign` command-line tool since before Xcode had this feature. – Jerry Krinock Jul 11 '17 at 01:51
1

In my case, under Xcode - General - Signing, the name in the Team field was not correct.

vomako
  • 8,262
  • 5
  • 32
  • 58
1

At least in Xcode 9.1, I had to choose the Team in Signing section (Target -> General pane). The team was already chosen but I had to choose it again to make the error disappear. It might have to do with developer certificate renewal.

epx
  • 1,025
  • 9
  • 16
1

I tried all of the above, in the end all I did was quit Xcode, open it up again, and toggle the iCloud capability off and on again.

Dave
  • 4,621
  • 7
  • 40
  • 56
0

Try - delete all provisioning profiles - go to Xcode->preference->account - add your apple id here (makes you easy to download profiles) - Click download profiles.

Prakash Raj
  • 1,935
  • 1
  • 14
  • 13
0
  1. I Turned on iCloud
  2. Set the Cloud kit Container through the Apple Developer dashboard to the app I needed
  3. Rename project bundle Identifier from the Xcode 10 and rename back to the original identifier after all fine
  4. Provisional profile got updated
KATJ Srinath
  • 830
  • 11
  • 14