NSCocoaErrorDomain

Hello! That definitely looks like a problem! I think that you’re encountering two separate issues: one with download cancellation and another with internal analytics. For the former issue, we’ll try to reproduce it on our side. It would be super helpful if you could file a feedback report in Feedback Assistant, making sure to attach sysdiagnose logs from the device on which asset-pack cancellation failed soon after reproducing the behavior. Plus, filing a feedback report ensures that you’ll be automatically notified when we fix the issue. We’ll let you know if we figure out a workaround before the fix is available. Thanks! The fact that version 0 of the asset pack with the ID X-XXXXXX-XXX finished being downloaded couldn't be reported: Error Domain=NSCocoaErrorDomain Code=3851 Property list invalid for format: 200 (property lists cannot contain objects of type 'CFError') That error message concerns the latter issue. If you installed the app from TestFlight, then the system collects data about success

The Apache logs tell you what the problem is: Error reading certificate file (../credentials/test_certificates.json): Error Domain=NSCocoaErrorDomain Code=260 The file doesn’t exist.UserInfo={NSUnderlyingError=Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory, NSURL=../credentials/test_certificates.json -- file:///home/azuki/, NSFilePath=/home/credentials/test_certificates.json} It's expecting to find the credentials in /home/credentials/ but they are not there, which means Apache wasn't running with the environment variable FPS_CERT_PATH set. If you cannot figure out how to set this variable for Apache in your environment, you could copy the credentials folder into /home/credentials/.

Thanks for the sugegstions I ran the curl with -v option [azuki@AlmaDevVM Key_Server_Module]$ curl -v -d @Test_Inputs/iOS/spc_v3_ios_uhd_no_lease_2048.json localhost:8080/fps * Trying ::1:8080... * Connected to localhost (::1) port 8080 (#0) > POST /fps HTTP/1.1 > Host: localhost:8080 > User-Agent: curl/7.76.1 > Accept: */* > Content-Length: 5947 > Content-Type: application/x-www-form-urlencoded > * Empty reply from server * Closing connection 0 curl: (52) Empty reply from server [azuki@AlmaDevVM Key_Server_Module]$ Also when I checked httpd logs I do see a couple of errors. [DEBUG] ❌ Assertion failure: paramErr (-42585) [src/parse_certificates.swift:36] src/parse_certificates.swift:13: Fatal error: 'try!' expression unexpectedly raised an error: src.FPSStatus.paramErr [Thu Jan 22 04:17:30.168292 2026] [core:notice] [pid 1004898:tid 1004898] AH00051: child pid 1009053 exit signal Illegal instruction (4), possible coredump in /etc/httpd timestamp=2026-01-22 04:18:01,830,FP_TOOLN=fpssdk,FP_

Hello, Thanks for your detailed explanation. ...yes, please file a bug on this and post the bug number back here. Sharing your bug number regarding this topic which I previously filed. FB21561068 https://feedbackassistant.apple.com/feedback/21561068 What's the scenario it's failing at? When determining whether the URL is in “trash” location by using API with the following steps, we are seeing a failure. Precondition: Download the attached sample project (TrashedFileURL.zip) in the feedback which I shared with you in above and build the TrashedFileURL.app from the project inside the zip folder. 1.Create a file in NSDocumentDirectory by TrashedFileURL.app. a.file:///private/var/mobile/Containers/Data/Application/{Application UUID}/Documents/{File UUID}.txt 2.Save the Bookmark of the file created in 1. in TrashedFileURL.app. 3.Delete the file by Files.app. 4.Get URL of the file from the Bookmark which is saved on TrashedFileURL.app. a.URL is referring a filepath which is inside of .Trash directory. file:///priva

the communication permission work for me with xcode and ios 26.2 public release it needs sync contacts and enable communication limit on the child device. the error messages I got from console were very helpful. (501) Invalidation handler invoked, clearing connection (501) personaAttributesForPersonaType for type:0 failed with error Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated from this process. UserInfo={NSDebugDescription=The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated from this process.} SendFlow (Host): Error sending begin message: hostViewControllerDidActivate(_:) Error Domain=AskToCore.ATMessageComposeValidationError Code=2 Contact syncing is not set up UserInfo={NSLocalizedDescription=Contact syncing is not set up, NSLocalizedFailureReason=Contact syncing needs to be configured before you can send messages., NSLocalizedRecoverySuggestion=Please enable contact syncing in Settings.} S

Regarding feedback FB20954846 for App Clip support, I got a message from Apple saying it is fixed. I can now compile, and code sign for an App Clip using the DeclaredAgeRange API. Great. Now that I can get past the compiler failure I'm running up against a new issue. When installed via TestFlight, an App Clip throws that the age range is unavailable. In the console app it looks like the App Clip is still prohibited from calling the system functionality: default PerformanceOrganizer AppClip 18:36:39.200071-0600 (501) Failed to fetch persona: got error from remote proxy: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} error PerformanceOrganizer AppClip 18:36:39.200108-0600 (50

SharedModelContainer.txt Folks who filed their feedback report may have gotten responses from the feedback system. For people who see the same issue but haven't yet filed any feedback report, I'd like to share our investigation here to hopefully help. To give you more context, SwiftData (with DefaultStore) uses Core Data as its underlying storage mechanism. At runtime, SwiftData converts the schema to an in-memory Core Data model (NSManagedObjectModel), and uses the model to load and persist the data store. Before system 26.1, when handling an attribute of an array type, SwiftData converts the array type to Binary Data. On system 26.1, it instead converts the type to Transformable. This change leads to a difference between the in-memory model and the model used in the persisted data store, triggering a migration error with the following message: Error Domain=NSCocoaErrorDomain Code=134140 Persistent store migration failed, missing mapping model.” To work around the issue, you might consider the follo