NSCocoaErrorDomain

FileRepresentation.importing's 'receivedData' is already deleted. when I use. import CoreTransferable struct Movie: Transferable { let url: URL static var transferRepresentation: some TransferRepresentation { FileRepresentation(contentType: .movie) { movie in SentTransferredFile(movie.url) } importing: { receivedData in let fileName = receivedData.file.lastPathComponent let copy: URL = FileManager.default.temporaryDirectory.appendingPathComponent(fileName) try FileManager.default.copyItem(at: receivedData.file, to: copy) return .init(url: copy) } } } Error Domain=NSCocoaErrorDomain Code=260 The file “IMG_0458.mov” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/private/var/mobile/Containers/Data/Application/D2E2AF9F-E879-4792-89CE-E7FB6B1B8234/tmp/.com.apple.Foundation.NSItemProvider.flbzCW/IMG_0458.mov, NSUnderlyingError=0x28389eeb0 {Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory}}

I'm seeing the same thing. Other issues that I have found searching around and see for the .well-known path on my own are clearly logged. For example:### Bad apple-app-site-association JSON: Error Domain=NSCocoaErrorDomain Code=3840 JSON text did not start with array or object and option to allow fragments not set. UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.}### Download URL 'https://<domain>/.well-known/apple-app-site-association' failed: -6717/0xFFFFE5C3 kFormatErrThat makes perfect sense because I do not have the file at .well-known. Generic HTML for a page not found page is returned. I do have the file at root and am seeing the exact same thing for that request- 0/0x0 noErr followed by an unexplained cancellation.

I am facing same problem. I got below error when trying to upload multiple images using background session configuration. Any help is appreciated. I am using uploadTask(with: request, fromFile: URL(fileURLWithPath: path)) for uploading images to server. These all things work fine if i upload 10 or less images at a time. But if i try to upload more tuan 10 then i got below errors. BackgroundSession <17817097-9127-45A7-B9C2-17145F5FD17F> error requesting a NSURLSessionUploadTask from background transfer daemon: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service with pid 65435 named com.apple.nsurlsessiond was interrupted, but the message was sent over an additional proxy and therefore this proxy has become invalid. UserInfo={NSDebugDescription=The connection to service with pid 65435 named com.apple.nsurlsessiond was interrupted, but the message was sent over an additional proxy and therefore this proxy has become invalid.

When launching Preview.app on the command line, I get an 'Operation not permitted' error returned. % /System/Applications/Preview.app/Contents/MacOS/Preview /Volumes/myfs/Through_the_pines.jpg 2024-06-17 14:23:16.826 Preview[2745:37915] PVImageContainer initWithURL:file:///Volumes/myfs/Through_the_pines.jpg failed, error = Error Domain=NSCocoaErrorDomain Code=257 The file “Through_the_pines.jpg” couldn’t be opened because you don’t have permission to view it. UserInfo={NSFilePath=/Volumes/myfs/Through_the_pines.jpg, NSUnderlyingError=0x6000022302a0 {Error Domain=NSPOSIXErrorDomain Code=1 Operation not permitted}} File permissions allow reading for all users: % ls -l /Volumes/myfs/Through_the_pines.jpg -rw-rw-r--@ 1 developer staff 2396454 Mar 25 10:48 /Volumes/myfs/Through_the_pines.jpg Am I right in assuming it's sandbox related?

Hey @eskimo :) Thanks for this clarification about notarisation :) Did it crash? Did that generate a crash report? No at all. When I try to run the application I saw these logs: Unable to register Error Domain=SMAppServiceErrorDomain Code=1 Operation not permitted UserInfo={NSLocalizedFailureReason=Operation not permitted} Received XPC error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named W4MF6H9XZ6.com.tonygo.NetworkMonitorApp.group.agent was invalidated: failed at lookup with error 3 - No such process. UserInfo={NSDebugDescription=The connection to service named W4MF6H9XZ6.com.tonygo.NetworkMonitorApp.group.agent was invalidated: failed at lookup with error 3 - No such process.} That makes totaly sense as the agent never starts ... I checked with the Console application like I usually did, but I see no messages. I put all my last changed on this branch: https://github.com/tony-go/NetworkMonitor/tree/sma-app-service

I'm running iOS 11 beta 8 and still getting the same error.Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.healthd.server was interrupted, but the message was sent over an additional proxy and therefore this proxy has become invalid. UserInfo={NSDebugDescription=The connection to service named com.apple.healthd.server was interrupted, but the message was sent over an additional proxy and therefore this proxy has become invalid.}I'm simply calling insertRouteData to insert 10 locations into the builder and it fails. Perhaps HKWorkoutRouteBuilder doesn't work on iOS. Perhaps HKWorkoutRouteBuilder isn't yet working in Beta 8 of iOS 11. Perhaps a workout session has to be open. Who knows? It just seems like creating a builder and inserting a few locations is the simplest use case that ought to simply work. I haven't even gotten to the point of calling finishRoute.

HI all: I have the same problem, my app is a normal swift project no other process involves, when it's running at the version after macOS 10.15.4, some users report that no system pop up to allow access to the Documents folder, after authentication by NSOpenPanel, And now we found this problem always exists in macOS 11.0 (Big Sur), After granting the permission by click NSOpenPanel confirm button, we grant the permission of user home path, but we can only access this folder, if you access its subfolder, it will give an error : Error Domain=NSCocoaErrorDomain Code=257 The file “Documents” couldn’t be opened because you don’t have permission to view it.. no system pop up alert, so my app not appearing in File and Folder permissions I don't know if any workaround here? did you found a solution?

Hello bweinsteinThank you for your answer. I have tested the posted code and some other extension on macOS Catalina beta with regular Safari and Safari Technology Preview. It seems to work fine on either as I haven't been able to reproduce the bug.I've also done some testing on macOS 10.14 with Safari Technology Preview, but it seems to function rather wierdly with it. I don't think the same issue happens, but some calls to API methods that use completion handlers don't seem work.I'm not sure how related to the original issue this is, but I do have another question. On all testing I've done, including on macOS Catalina, from time to time I get this error in the XCode console: Error connecting back to host app: NSCocoaErrorDomain, code: 4099 and much more rarely the same error but with code 4097. Is this message related to the original problem? What causes it?Thank you for your time.

Error loading /var/containers/Bundle/Application/FF057050-1BCC-49D8-9D3F-A3731E30F354/.app/PlugIns/.xctest/Tests (133): dlopen(/var/containers/Bundle/Application/FF057050-1BCC-49D8-9D3F-A3731E30F354/.app/PlugIns/.xctest/Tests, 0x0109): Symbol not found: _$s5Model11AccountDataV7TestingE4mockACvau Referenced from: <4027FFAF-5C6C-3F8A-9862-648D3D4A1257> /private/var/containers/Bundle/Application/FF057050-1BCC-49D8-9D3F-A3731E30F354/.app/PlugIns/.xctest/Tests Expected in: <406DF294-634D-3D8A-8E59-BEE455BA96AF> /System/Developer/Library/Frameworks/Testing.framework/Testing Failed to load test bundle from file:///private/var/containers/Bundle/Application/FF057050-1BCC-49D8-9D3F-A3731E30F354/.app/PlugIns/.xctest/: Error Domain=NSCocoaErrorDomain Code=3588

Me too. Here's the details: Domain: DVTDownloadableErrorDomain Code: -1 User Info: { DVTErrorCreationDateKey = 2024-01-30 21:45:16 +0000; } -- Unable to deserialize downloadables index request data. Domain: DVTDownloadableErrorDomain Code: 6 User Info: { URL = https://devimages-cdn.apple.com/downloads/xcode/simulators/index2.dvtdownloadableindex; } -- The data couldn’t be read because it isn’t in the correct format. Domain: NSCocoaErrorDomain Code: 3840 Failure Reason: The data is not in the correct format. User Info: { NSDebugDescription = Cannot parse a NULL or zero-length data; } -- System Information macOS Version 14.3 (Build 23D56) Xcode 15.2 (22503) (Build 15C500b) Timestamp: 2024-01-30T18:45:16-03:00

Thanks for the extra info. I see two errors here: The top-level error is NSCocoaErrorDomain code 4, which is NSFileNoSuchFileError. The underlying error is NSPOSIXErrorDomain code 2, which is ENOENT. Cocoa errors can be a bit ‘squishy’, meaning that the same error can come from a variety different sources. However, the presence of the ENOENT error suggests that this really is a file not found problem of some form. It looks like the source file is in the Downloads folder. That might be important because that folder is protected by MAC [1]. If you use the Finder to move the file to your home directory and then drag the file on to your app, does that work? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] That’s another topic I cover in On File System Permissions.

Sorry but i can't understand how this work. In documentation write, create an app-scoped bookmark for that folder, ok, im tryNSURL *openPanelFileURL = [NSURL URLWithString:[urlString stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding]];NSError *error = nil; BOOL bookmarkDataIsStale;NSData *bookmarkData = nil;bookmarkData = [openPanelFileURL bookmarkDataWithOptions:NSURLBookmarkCreationWithSecurityScope includingResourceValuesForKeys:nil relativeToURL:nil error:&error];if (error) { NSLog(@Error creating bookmark for URL (%@): %@, urlString, error); [NSApp presentError:error];but see error in terminalError creating bookmark for URL (/Users/username/Desktop/test/): Error Domain=NSCocoaErrorDomain Code=262 Scoped bookmarks can only be made with file URLs UserInfo={NSURL=/Users/username/Desktop/test/, NSDebugDescription=Scoped bookmarks can only be made with file URLs}Your need create app-scoped for folder, but your can't create app-scoped for folder ??? ***???What wrong?

MLModelCollection.beginAccessing(identifier: Collection Name) { result in var modelURL: URL? switch result { case .success(let collection): print(collection) modelURL = collection.entries[io.aben.animegan2face.v1]?.modelURL case .failure(let error): print(error) } print(modelURL as Any) } Got failure error: MLModelCollection: namespace (animegan2face_paint_512_v2) registration failed. Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.triald.namespace-management was invalidated: failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.triald.namespace-management was invalidated: failed at lookup with error 159 - Sandbox restriction.} Error Domain=com.apple.CoreML Code=10 Failed to begin access for model collection with identifier 'animegan2face_paint_512_v2': invalid identifier UserInfo={NSLocalizedDescription=Failed to begin access for model collection with identifier 'animegan2face_paint_512_v2': i

Does anyone see the same problem on macOS 14.7.1? I've received multiple reports from users that macOS 14.7.1 cannot create new bookmarks or resolve existing bookmarks. Same error message: Error Domain=NSCocoaErrorDomain Code=256 Failed to retrieve app-scope key UserInfo={NSDebugDescription=Failed to retrieve app-scope key} All users updated from macOS 13.* Ventura to macOS 14.7.1 Sonoma, which triggered the issue Restarting Mac does not fix the issue Clearing all app data does not resolve the issue One user reported that using bookmarks on a new macOS user account works correctly. This leads me to believe that the macOS keychain for their user account is broken. See also https://developer.apple.com/forums/thread/46583 Does upgrading from macOS 13 to macOS 14.7.1 break the keychain?

An Apple engineer has provided me the following explanation:The app could not communicate with a helper application (i.e. the photo library). The most common reason that assetsd might crash is because the foreground app is using a lot of memory (or allocating memory very quickly), and the system decides to terminate assetsd to alleviate some of that memory pressure.To prevent these errors, you should make sure that your app is not triggering a high memory pressure situation.This should only be a temporary issue. In other words, if you tried to submit the same request later, it may work (assuming that any high memory pressure situation has been resolved). So, I recommend that you queue up requests that fail and try to submit them later, and inform your user of this in some way, so that they know the save has not gone through yet.This same issue can also create an error with the code 4099, domain NSCocoaErrorDomain and the description:Couldn’t communicate with a helper application.