NSCocoaErrorDomain

Oh blah, I shoulda scrolled down )-: The above is my response to your first post. The following is in response to your subsequent ones. I'm sorry I already tried to shorten it up - and failed :-D Thank you for reading through! The former approach only works when you’re installing the agent yourself, because you control the entire launchd property list. Use the latter approach if you’re using SMAppService to install your agent. I was actually using SMAppService.agent(plistName: )the whole time, I just took the information about the Bundle Identifier in AppSandboxLoginItemXPCDemo because I couldn't make the way with just the groups work. That was what I originally tried but never worked and I thought this is the way to do it. Or am I using this wrong? I'm copying the plist file with a build phase to Destination Wrapper into Contents/Library/LaunchAgents. This is the SMAppService way or do I have to do something different? Or is this mixed way between AppService and LoginItem? instead of using a command line tar

Well - I think I found my problem and wow it's a weird one. After reading all the sample code related to XPC again and adding my teamID again to the bundle identifier (XXXXXXXXX.com.myapp.helper) I saw Xcode replacing the first character of the teamID with a dash - It always did that and I put that to Xcode weirdness Because bundle Identifiers are reverse dns format this should obviously not start with a digit - well unlucky situation here Well now this is a problem. My TeamIdentifier starts with a 4. My bundleID 4T9XXXXXX.com.myapp.helper gets immediately after submitting the textfield replaced with -T9XXXXXX.com.myapp.helper. When I build the App and check its contents Info.plist - the bundleidentifer is the wrong one with a dash. I think this took me all over the place because I ignored it for year when I saw it. After setting the Product Name and bundle Identifiers manually, it took some tries of changing the plist but after some tries it did stick. after reviewing again AppSandboxLoginitemXPCDemo readme

I'm also having problem with Replace Container on real device. Even when I tried to create new iOS application to test it, when I replace the container, the application crashes. Easy way to replicate problem: Step 1: In Xcode, using project template, create new iOS application with CoreData support. Step 2: Build application and run it on real device with iOS 17. Step 3: Download Container for this application using Xcode. {menu - Window - Devices and Simulator). Step 4: Replace Container (the same container previously downloaded) using Xcode {menu - Window - Devices and Simulator). Step 5: Run application again on real device = crash/error. Errors: error: Failed to create directory: NSCocoaErrorDomain (513) CoreData: Unhandled exception finding default Directory URL '+[NSPersistentContainer defaultDirectoryURL] Could not conjure up a useful location for writing persistent stores.' My system configuration for development: Xcode 15.0.1 (also tested with Xcode 15.1 beta 3 with same error) iOS 17.1.2, i

This problem is not repaired in Xcode 15.1 beta 3! This is a serious error that can be easily provoked: in the Window menu, select Device and Simulators, Download Container... and immediately Replace Container... with the one you just downloaded. When the app tries to access the file in .../Library/Application Support, the following error message appears: Thread 1: Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=NSCocoaErrorDomain Code=513 Du hast nicht die Zugriffsrechte, um die Datei „Application Support“ im Ordner „Library“ zu sichern. UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/F2ACE0F7-9446-46B7-8B82-AD269E62C2A1/Library/Application Support, NSUnderlyingError=0x2812861c0 {Error Domain=NSPOSIXErrorDomain Code=13 Permission denied}} Unfortunately this problem prevents us from testing and further developing our app.

I notice that once I open a second ModelContainer on same URL as the document that's open in the DocumentGroup, then all saves to the DocumentGroup's model container fail with: Error saving the database Error Domain=NSCocoaErrorDomain Code=134020 The model configuration used to open the store is incompatible with the one that was used to create the store. UserInfo={NSAffectedObjectsErrorKey= (entity: Blah; id: 0x60000026e0c0 ; data: { id = 91E56F61-CFE0-42E4-9EA9-EAD4256B64AB; imageData = nil; name = Untitled Blah; })} I will assume that this is just not a good idea right now, and conclude that Document based SwiftData apps do not work well with multiple scenes.

NSStoreModelVersionHashesDigest = DJ2WYYwgxZ0ODDxWSCU/qENUGNTyxR4QfG8zLErpzQrvMoo9u19pSVjC7jzbUm0QLzGhFtKR3E0LRQvO9u6WXQ==; NSStoreModelVersionHashesVersion = 3; NSStoreModelVersionIdentifiers = ( 1.0.0 ); NSStoreType = SQLite; NSStoreUUID = FC5CF467-5684-4C95-8C0E-49698D0A8648; _NSAutoVacuumLevel = 2; }, reason=The model used to open the store is incompatible with the one used to create the store}}, reason=Failed to open the store} with userInfo { NSUnderlyingError = Error Domain=NSCocoaErrorDomain Code=134100 The managed object model version used to open the persistent store is incompatible with the one that was used to create the persistent store. UserInfo={metadata={n NSPersistenceFrameworkVersion = 1337;n NSStoreModelVersionChecksumKey = /mv+MJ232k6TtgLWF/6u6Xvt1IOs/ezBTew3e5ULc+E=;n NSStoreModelVersionHashes = {n CloudSyncModelA = {length = 32, bytes = 0x3987992e 6ee680c6 e8bb9511 266ac8b2 ... 97ac3feb daf3a616 };n CloudSyncModelB = {length = 32, bytes = 0xd2664c00 d176a085 d0cb6b7f 7fdd3661 ..

CoreData: error: addPersistentStoreWithType:configuration:URL:options:error: returned error NSCocoaErrorDomain (134100) CoreData: error: userInfo: CoreData: error: metadata : { NSPersistenceFrameworkVersion = 1337; NSStoreModelVersionChecksumKey = /mv+MJ232k6TtgLWF/6u6Xvt1IOs/ezBTew3e5ULc+E=; NSStoreModelVersionHashes = { CloudSyncModelA = {length = 32, bytes = 0x3987992e 6ee680c6 e8bb9511 266ac8b2 ... 97ac3feb daf3a616 }; CloudSyncModelB = {length = 32, bytes = 0xd2664c00 d176a085 d0cb6b7f 7fdd3661 ... 60f1b0b2 a9d0444e }; CloudSyncModelC = {length = 32, bytes = 0xca91943c 6571aedb 07473eaa 154207d1 ... 66bb77c1 6283438e }; }; NSStoreModelVersionHashesDigest = DJ2WYYwgxZ0ODDxWSCU/qENUGNTyxR4QfG8zLErpzQrvMoo9u19pSVjC7jzbUm0QLzGhFtKR3E0LRQvO9u6WXQ==; NSStoreModelVersionHashesVersion = 3; NSStoreModelVersionIdentifiers = ( 1.0.0 ); NSStoreType = SQLite; NSStoreUUID = FC5CF467-5684-4C95-8C0E-49698D0A8648; _NSAutoVacuumLevel = 2; } CoreData: error: reason : The model used to open the store is incompatibl

CoreData: error: URL: file:///private/var/mobile/Containers/Shared/AppGroup/98EF0668-1D20-4B71-967F-E5D8F9FB3027/Library/Application%20Support/default.store CoreData: error: : Attempting recovery from error encountered during addPersistentStore: 0x283fe4030 Error Domain=NSCocoaErrorDomain Code=512 The file couldn’t be saved. UserInfo={reason=Failed to create file; code = 2} CoreData: error: During recovery, parent directory path reported as missing CoreData: error: Recovery attempt while adding (type: SQLite, url: file:///private/var/mobile/Containers/Shared/AppGroup/98EF0668-1D20-4B71-967F-E5D8F9FB3027/Library/Application%20Support/default.store) was successful! CoreData: error: Could not materialize Objective-C class named Array from declared attribute value type Array of attribute named images CoreData: error: (1) I/O error for database at /private/var/mobile/Containers/Shared/AppGroup/98EF0668-1D20-4B71-967F-E5D8F9FB3027/Library/Application Support/default.store. SQLite error code:1, 'no such ta

Well if i launch from fresh install i get CoreData: error: Failed to stat path '/private/var/mobile/Containers/Shared/AppGroup/98EF0668-1D20-4B71-967F-E5D8F9FB3027/Library/Application Support/default.store', errno 2 / No such file or directory. CoreData: error: Executing as effective user 501 CoreData: error: Failed to statfs file; errno 2 / No such file or directory. CoreData: error: Logging status information for directory path: /private/var/mobile/Containers/Shared/AppGroup/98EF0668-1D20-4B71-967F-E5D8F9FB3027/Library/Application Support CoreData: error: Executing as effective user 501 CoreData: error: Information for / CoreData: error: File Device ID: 0 CoreData: error: Device ID: 838860801 CoreData: error: File Size: 544 bytes CoreData: error: File inode: 2 CoreData: error: File user ID: 0 CoreData: error: File group ID: 0 CoreData: error: File Permissions: CoreData: error: d CoreData: error: 755 CoreData: error: component is not a symbolic link CoreData: error: component is readable CoreData: error: com