This problem happens to me in an iOS share extension. I haven't tried the main app.

I suggest you to user recordID in the method -[CKContainer fetchUserRecordIDWithCompletionHandler:] when you create a subscription. You should cache the user recordID. And next time when you see the curreent user recordID is different from the cached one, you can assume the iCloud account logged in has changed. Then you just create another subscription with the most recent user recordID.

Still an issue.

It turns out the loop exists in such a scenario: Device A Core Data changes -> CloudKit changes -> Push notification -> Device B Core Data changes -> (repeatedly) CloudKit changes -> Push notification -> Device A Core Data changes -> ........

Same issue.

I have the same question

Is this still an issue?

Jan 14, 2022. Is deleting containers supported now? At least, we need the ability to delete the containers that are not deployed to production.

This is also a problem in my app.

This is an issue to me as well.

I can confirm this is still an issue as of October 2022

Same problem here.

Same problem here.

See screenshot