@meaton iCloud Private Relay is giving users a false of security to users if there are no settings to enforce its use. (i.e. no safari if iCloud Private Relay is not available)
MycroftCanner
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
From
London, England
Post
Replies
Boosts
Views
Activity
Seems to be the same issue as https://developer.apple.com/forums/thread/7628
I still get random EXC_BAD_ACCESS crashing in iOS 14.7 using fetchedObjects or even using object(at:).
let batch = (beforeUpdate..<afterUpdate).map { controller.object(at: .init(row: $0, section: 0)) }
The weird thing right after the crash in the debugger I can access the object at that row without problem:
(lldb) p controller.fetchedObjects![$0]
(NSFetchRequestResult) $R9 = (object = 0x0000000280fac9b0)
(lldb) p $0
(Int) $R7 = 200
(lldb) p controller.object(at: .init(row: $0, section: 0)) as? NSManagedObject
(NSManagedObject?) $R6 = 0x0000000280fac9b0 {
baseCDContact@0 = {
The good news is that this issue seems to be fixed in the iOS 15 beta...
Alternatively, you can use two persistent stores, one local and one CloudKit. You'll put the entities in different Configurations and add them to the same NSPersistentStoreCoordinator. The entities in the local configuration can use any Core Data features including unique constraints. You'd use persistent history and the notifications to drive importing and exporting between the two store files. This is more customizable but obviously a considerable amount of work.
Do you have some example for this?
Works fine for me in 14.5
NotificationCenter.default
.publisher(for: ASAuthorizationAppleIDProvider.credentialRevokedNotification)