NSCocoaErrorDomain

I also tried changing the method of deletion to the following. This tries to delete entity Object that has a to-many relationship children: [Child]. guard let id = object.id else { return } do { try container.mainContext.delete(model: Object.self, where: #Predicate { object in object.id == id }) } catch { print(error) } This does not crash the app, but fails to delete the entity with the following console output: Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={Reason=Entity named:Object not found for relationship named:children, MissingEntity=Object. () ... I'm not sure what this means, perhaps someone more clever will find it useful. @DTS Engineer

More log details: com.apple.securityd debug 09:13:29.674468-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network default: NO com.apple.securityd debug 09:13:29.674577-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network blocked: YES com.apple.securityd debug 09:13:29.674621-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network blocked: YES com.apple.securityd debug 09:13:29.674952-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network blocked: YES com.apple.securityd debug 09:13:29.675103-0500 SecurityAgentHelper-arm64 xpc no query dict to determine whether for system keychain: Error Domain=NSOSStatusErrorDomain Code=-50 no object for key query (paramErr: error in user parameter list) UserInfo={numberOfErrorsDeep=0, NSDescription=no object for key query} com.apple.securityd default 09:13:29.675178-0500 SecurityAgentHelper-arm64 SecCritical Failed to talk to trustd after 4 attempts. com.apple.securityd debug 09:13:29.675329-0500 SecurityAgentHelper-arm64 xpc no query di

Ok Great! I have created my VersionedSchemas that define my four models and included them in the models property. And created my ModelContainer using the schema initializer Schema(versionedSchema: SchemaV2.self) Yet nothing works. I'm getting a few errors including: error: Attempting to retrieve an NSManagedObjectModel version checksum while the model is still editable. This may result in an unstable verison checksum. Add model to NSPersistentStoreCoordinator and try again. and error: Store failed to load. (type: SQLite, url: with error = Error Domain=NSCocoaErrorDomain Code=134504 Cannot use staged migration with an unknown model version. UserInfo={NSLocalizedDescription=Cannot use staged migration with an unknown model version.} with userInfo { NSLocalizedDescription = Cannot use staged migration with an unknown model version.; } I’m concerned that I may have corrupted my database with all the things I’ve been trying. Is there a chance that the database is corrupted, or is there something fundame

same for me using google maps foe iOS. maybe a google issue, Burt for sure apple does not help finding what. Google Maps SDK for iOS version: 8.4.0.0 Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process. UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}

I'm developing an application that uses hardlinks to track certain files created by the app. Initially, before the hardlink is created, the files behave as expected. For example, if the app generates a .number file, I can open and edit it with Numbers without any issues. However, once the hardlink is created, the file appears locked, and Numbers can no longer write to it. What are you actually trying to do here and why are hardlinks important here? The problem here is, setting the immediate issue aside, I'm not sure this will actually work very well in practice. Two problems I see off the top of my head: The standard safe save architecture works by having apps modify a copy of the file, the (ideally, atomically) exchange the new file with the old file. On file system that specifically this atomic operation (APFS and HFS+), I think that your hard link will still work. However, on all other file systems your hardlink will fail (as the new file is in fact a new file). In addition, I don't know what will happen i