See screenshot
fysteven
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Same problem here.
Same problem here.
Reply to
Error with initialise of persistent storage since 13.2 - The file “***” couldn’t be opened.
I can confirm this is still an issue as of October 2022
This is an issue to me as well.
This is also a problem in my app.
Jan 14, 2022. Is deleting containers supported now? At least, we need the ability to delete the containers that are not deployed to production.
Is this still an issue?
I have the same question
Same 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 -> ........
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.
This problem happens to me in an iOS share extension. I haven't tried the main app.