NSCocoaErrorDomain

May I add your wei xin(fang zhi he xie)? my wei xin is rock_homeboy and my dian hua hao ma is 18616309756, Im a RD of ByteDance(Douyin), and I have encountered the same problem as you mentioned above, currently contacting the user so that I can provide disk and system log diagnosis to Apple.Let me describe the problem:1.Failed to create file through NSFileManager function- (BOOL)createFileAtPath:(NSString *)path contents:(nullable NSData *)data attributes:(nullable NSDictionary<nsfileattributekey, id=> *)attr;The error information obtained by printing errno and strerror (errno) is as follows:errorCode = 17, errorDesc = File exists.The following key file attributes are provided:{ NSFileCreationDate = 1970-01-01 00:00:02 +0000; NSFilePosixPermissions = 493; NSFileSystemNumber = 16777222; NSFileType = NSFileTypeDirectory; }2.Can't write to file using NSData- (BOOL)writeToFile:(NSString *)path options:(NSDataWritingOptions)writeOptionsMask error:(NSError **)errorPtr; error: Error Domain=NSCocoaErrorDomain

Hi VMdominguez,I'm getting the same error. Are you able to confirm in your console logs of the device:*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSCFConstantString stringByAppendingString:]: nil argument' *** First throw call stack: (0x1b81d0164 0x1b7ee4c1c 0x1b848e5b8 0x1e3faef54 0x1e3fac914 0x1023df684 0x1023e2f30 0x1b7e6eec4 0x1b7e7033c 0x1b7e727b4 0x1b7e7f5c0 0x1b7e7fd9c 0x1b7ed76d8 0x1b7edd9c8)Looks like the KerberosExtension Process crashes, (Note the animation of the new SSOExtension disappears really fast after entering your password and hitting enter)The crashes should be generating logs and found in:iPhone > Settings > Privacy > Analytics & Improvements > Analytics Data > KerberosExtensionSSO.logGeneration of SysDiagnostics.logs: https://developer.apple.com/bug-reporting/profiles-and-logs/Instructions: https://download.developer.apple.com/iOS/iOS_Logs/Single_SignOn_Diagnostics_Logging_Instructions.pdfEdit:Check out this error too,

If revevant, I'm seeing these issues while debugging in Xcode, however they may be basic/expected type errors as I am not able to reproduce the issue on my machine anyway.objc[99539]: Class AMSupportURLConnectionDelegate is implemented in both /System/Library/PrivateFrameworks/OSPersonalization.framework/Versions/A/OSPersonalization (0x7fff8b54cb68) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x103cfb228). One of the two will be used. Which one is undefined. objc[99539]: Class AMSupportURLSession is implemented in both /System/Library/PrivateFrameworks/OSPersonalization.framework/Versions/A/OSPersonalization (0x7fff8b54cbb8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x103cfb278). One of the two will be used. Which one is undefined. 2020-05-21 11:09:44.426694-0400 Safari[99539:37398753] Metal API Validation Enabled 2020-05-21 11:09:46.158099-0400 Safari[99539:37398994] Bogus event on event stream listener. 2020-05-21 11:09:46

I've been in touch with Rich Kubota who is working to get to the bottom of the ODR request issue. He was able to reproduce the error with my app and capture device logs to help the ODR engineers track down the issue. To be clear, the error that's being returned by a request for any ODR: Error Domain=NSCocoaErrorDomain Code=4994 The requested application data doesn’t exist. UserInfo={NSUnderlyingError=0x281b6a730 {Error Domain=_NSBundleResourceRequestErrorDomain Code=100 No manfiest found for bundle ID com.xxxxxx UserInfo={NSLocalizedFailureReason=No manfiest found for bundle ID com.xxxxxx}}} (where com.xxxxxx is the bundle ID of my app) (and note the typo manfiest 😐) Again, ODR works for me in TestFlight and every other configuration I'm able to try, only fails in App Review.I received this message from Rich last Friday 5/29: I finally managed to get the ODR engineer set up with the App Review Network administrator to provide the info needed to investigate this issue. It’s unfortunate that this is t

I'm also experiencing a similar issue. One user (out of thousands) is getting a 512 error – NSFileWriteUnknownError when the iOS app attempts to write a file to the caches directory or the documents directory.The user is on iOS 13.3, and logging the error shows Error Domain=NSCocoaErrorDomain Code=512 The file couldn’t be saved. UserInfo={NSUserStringVariant=Folder}

However, if I then uncheck that box and launch my app again, it gets killed right away. I agree that this is unexpected. I repeated your test here in my office and it’s not what I saw. Specifically, I created a new test app and added this code to access Documents: do { ttprint(will get doc dir) ttlet docDir = try FileManager.default.url(for: .documentDirectory, in: .userDomainMask, appropriateFor: nil, create: true) ttprint(will list doc dir) ttlet docContents = try FileManager.default.contentsOfDirectory(at: docDir, includingPropertiesForKeys: nil, options: []) ttprint(did list doc dir, contents: (docContents)) } catch { ttprint(error) } When I ran the app after revoking the app’s access to Documents, I saw this: will get doc dir will list doc dir Error Domain=NSCocoaErrorDomain Code=257 The file “Documents” couldn’t be opened because you don’t have permission to view it. UserInfo={NSURL=file:///Users/quinn/Documents, NSFilePath=/Users/quinn/Documents, NSUnderlyingError=0x600000cb6130 {Error Domain=

@bens OSLogStore is marked available in iOS 14: https://developer.apple.com/documentation/oslog/oslogstore?changes=latest_minor Unfortunately, there is an issue with retrieving entries (the which I asked about during labs and have filed a Feedback Request for. Please duplicate if you get a chance!: FB7787937 This is for the error message: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service on pid 0 named com.apple.OSLogService was invalidated.

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?