Search results for

NSCocoaErrorDomain

1,063 results found

Post

Replies

Boosts

Views

Activity

Failed to load test bundle from file, Error Domain=NSCocoaErrorDomain Code=3588
I have developed an app and its working fine, I decide to add Unit-Testing to the project while running the test on the device, Xcode throws me an error -> Failed to load test bundle from file:///private/var/containers/Bundle/Application/07F796E0-3BCE-4DF9-91E9-4D69E9B94F43/aspas%20dev.app/PlugIns/aspasDevTests.xctest/: Error Domain=NSCocoaErrorDomain Code=3588 dlopen(/var/containers/Bundle/Application/07F796E0-3BCE-4DF9-91E9-4D69E9B94F43/aspas dev.app/PlugIns/aspasDevTests.xctest/aspasDevTests, 0x0109): -> The bundle “aspasDevTests” couldn’t be loaded. Try reinstalling the bundle. I tried many things but nothing is working, needed help in the issue, Thanks in advance
2
0
3.1k
Mar ’23
I am creating keyboard with UIInputViewController and has this debug output. Anyone knows how to silent this.
2023-03-15 16:49:27.504266-0400 Flip[32191:1879406] [WindowServer] Failed to register for CADisplay change notifications: 0x9 2023-03-15 16:49:27.505090-0400 Flip[32191:1879406] [WindowServer] Failed to register for CADisplay power notifications: 0x9 2023-03-15 16:49:27.549439-0400 Flip[32191:1879406] [Common] BKSAccelerometer unable to create notifyd token for device orientation 2023-03-15 16:49:27.549252-0400 Flip[32191:1879672] [default] Failed to register for server availability: 9 2023-03-15 16:49:27.736276-0400 Flip[32191:1879406] [Default] Unable to register for test daemon availability notification. 2023-03-15 16:49:27.737912-0400 Flip[32191:1879406] [Default] Unable to register token for checking test daemon availability. 2023-03-15 16:49:27.739657-0400 Flip[32191:1879406] [Default] Unable to register for test daemon availability notification. 2023-03-15 16:49:27.741339-0400 Flip[32191:1879406] [Default] Unable to register token for checking test daemon availability. 2023-03-15 16:49:27.743108-0400 F
3
0
658
Mar ’23
Reply to CoreData stack init is freeze
I decided to apply my previous attempts on the original WAL file. First, the checkpoint forcing via journal_mode=DELETE doesn't work for the original WAL file. The CoreData is freeze and file is not removed at the end of session. Second, I moved (didn't copy) original file under different name myDB2.sqlite and the CoreData stack init is freeze again. Interesting in my previous tests that the copied file with the same name was opened but with periodic errors. Third, If the original file is moved and copied to the path with initial name then the CoreData stack initialized successfully and opened the DB. The addPersistentStoreWithType:configuration:URL:options:error: func started to return the error: ... CoreData: error: sourceURL : file:///var/mobile/Containers/Data/Application/08D158CE-7216-4271-A3F2-AF3E4E5DA772/Documents/myDB.sqlite CoreData: error: reason : Cannot migrate store in-place: error during SQL execution : database or disk is full CoreData: error: destinationURL : file:///var/mobile/Containers/Dat
Mar ’23
PHPicker fails to load RAW images
We observed that the PHPicker is unable to load RAW images captured on an iPhone in some scenarios. And it is also somehow related to iCloud. Here is the setup: The PHPickerViewController is configured with preferredAssetRepresentationMode = .current to avoid transcoding. The image is loaded from the item provider like this: if itemProvider.hasItemConformingToTypeIdentifier(kUTTypeImage) { itemProvider.loadFileRepresentation(forTypeIdentifier: kUTTypeImage) { url, error in // work } } This usually works, also for RAW images. However, when trying to load a RAW image that has just been captured with the iPhone, the loading fails with the following errors on the console: [claims] 43A5D3B2-84CD-488D-B9E4-19F9ED5F39EB grantAccessClaim reply is an error: Error Domain=NSCocoaErrorDomain Code=4097 Couldn’t communicate with a helper application. UserInfo={NSUnderlyingError=0x2804a8e70 {Error Domain=NSCocoaErrorDomain Code=4097 connection from pid 19420 on anonymousListener or serviceListener UserInfo
7
0
2.9k
Mar ’23
UNNotificationCenter API arbitrary failures, loses connection with NotificationCenter daemon
Hi. My MacOS application (Obj-C, Cocoa MacOS 10.15 or later) sets itself as delegate for UNNotificationCenter, and implements both - (void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions))completionHandler and - (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(nonnull UNNotificationResponse *)response withCompletionHandler:(nonnull void (^)(void))completionHandler It creates and schedules many user-notifications (mostly with no trigger meaning - present to the user ASAP and sometimes 2.5 seconds in the future, so to group notifications better. Each notification is also holding som dictionary of UserInfo containing some data. My AppDelegates handles user responses (both standard open, cancellation, and cancel-all) and also custom user-actions I attach to the category. All works well on most Macs and almost always. However - On few Macs
0
0
912
Feb ’23
An error occurred during persistent store migration (CoreData)
I added new model version and select it like default one. Then I added new attribute to existing entity in new model version. To test migration I installed previous version of app and add filled with all data in app. Then I install new changes and it work on simulator. If I move that build to TestFlight and test via real device then I get this error: Fatal error: ###persistentContainer: Failed to load persistent stores:Error Domain=NSCocoaErrorDomain Code=134110 An error occurred during persistent store migration. UserInfo={sourceURL=file:///private/var/mobile/Containers/Shared/AppGroup/DBB80C75-1B07-4318-8BA3-3F4FFC14FBD7/AppName.sqlite, reason=Cannot migrate store in-place: near null: syntax error, destinationURL=file:///private/var/mobile/Containers/Shared/AppGroup/DBB80C75-1B07-4318-8BA3-3F4FFC14FBD7/AppName.sqlite, NSUnderlyingError=0x281958180 {Error Domain=NSCocoaErrorDomain Code=134110 An error occurred during persistent store migration. UserInfo={reason=near null: syntax error, NSSQ
1
0
1.9k
Feb ’23
Error -24169 returned by authserver when using altool
Hi, I am trying to run xcrun altool --list-providers -u my@email.com -p my-application-specific-password My console response looks as follows with a -24169 error when trying to authenticate. I have used this application password in the past with fastlane, but I do not seem to be able to authenticate today. 2023-02-17 10:09:28.753 Initializing bundle from: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework 2023-02-17 10:09:28.762 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2023-02-17 10:09:28.762 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2023-02-17 10:09:28.762 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iT
2
0
1.1k
Feb ’23
XPC connection invalidated when Background Processing task performs a network request
Hello, I'm developing an iOS app which has an ability to upload user photos, and I'm using a Background processing task to perform such an operation. The app also has File provider extension, which is involved in the process Whenever the background task is launched, the following actions are performed: Main app fetches new items from PHAsset library and copies them to our file storage File Provider extension uploads those items to a cloud storage Everything goes fine until Extension tries to perform a network request, at this point I'm getting the following error: (501) got error from remote proxy: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.mobile.usermanagerd.xpc was invalidated: failed at lookup with error 159 - Sandbox restriction.} App has all the required entitlements and extension and main
0
0
1.7k
Feb ’23
Reply to nsurlsessiond disconnects on queuing several upload tasks
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.
Topic: App & System Services SubTopic: General Tags:
Feb ’23
Reply to Cannot create instance of NSSavePanel
I'm fairly certain it's related to entitlements and possible App Groups. I'm now getting : [OpenSavePanels] Unable to display save panel (unrecognized error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service created from an endpoint was invalidated from this process. UserInfo={NSDebugDescription=The connection to service created from an endpoint was invalidated from this process.})
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Feb ’23
Cannot create instance of NSSavePanel
I've recently migrated my MacOS app to deployment target 12.0 and when I try to create an instance of NSSavePanel, like this: let panel = NSSavePanel() I get the following error: 2023-02-07 18:11:49.362237+0100 Acsy[31010:8797816] [miscellany] CLIENT ERROR: remote view delegate NSSavePanel lacks method which can react to the details of Error Domain=NSCocoaErrorDomain Code=4097 connection to service created from an endpoint UserInfo={NSDebugDescription=connection to service created from an endpoint} 2023-02-07 18:11:49.362584+0100 Acsy[31010:8797816] [OpenSavePanels] Unable to display save panel (unrecognized error: Error Domain=NSCocoaErrorDomain Code=4097 connection to service created from an endpoint UserInfo={NSDebugDescription=connection to service created from an endpoint}) Any ideas what this means? This used to work MacOS 11.5. I'm on Xcode 14.1 / Ventura 13.0 entitlements: com.apple.security.files.user-selected.read-write is set to true
6
0
1.4k
Feb ’23
In-app purchase fails on Apple Silicon Mac
I'm testing IPhone and iPad Apps on Apple Silicon Macs. When I purchase In-app product in the app on Apple Silicon Mac, the payment receipt is not created, so the purchase fails. In console log, it says it doesn't have permission to write to the file. storekitagent [6913DE38_SK1] Error writing receipt (5095 bytes) to file:///Users/XXXX/Library/Containers/90FE2A60-9FDF-4ECF-848F-CE3D396322CA/Data/StoreKit/sandboxReceipt: Error Domain=NSCocoaErrorDomain Code=513 You don’t have permission to save the file “sandboxReceipt” in the folder “StoreKit” UserInfo={NSFilePath=/Users/XXXX/Library/Containers/90FE2A60-9FDF-4ECF-848F-CE3D396322CA/Data/StoreKit/sandboxReceipt, NSUnderlyingError=0x14202c920 {Error Domain=NSPOSIXErrorDomain Code=1 Operation not permitted}} The App is using Original API for In-App Purchase written in Objective-C. When I purchase in-app product, the app calls SKPaymentQueue::addPayment. And then it gets paymentQueue:updatedTransactions callback with SKPaymentTransactionStatePurchased. Th
7
0
1.5k
Feb ’23
NSPOSIXErrorDomain Code=24 "Too many open files"
I am trying to write a line of data into txt file every 30 seconds and in each time I have open the file and close it carefully. (It will be run between two threads.For example this method is run in thread-A and call itself in thread-B, and in thread-B it call itself again and run in thread-A) When my app runs for a long time(for example one night), it will give this error message: DebugLog:failed to append: Error Domain=NSCocoaErrorDomain Code=512 (null) UserInfo={NSFilePath=/var/mobile/Containers/Data /Application/DC61A031-1102-4D28-A28D-AD17E2AF0511/Documents/AppLogL1_1.txt, NSUnderlyingError=0x283c8fba0 {Error Domain=NSPOSIXErrorDomain Code=24 Too many open files}} Can anyone tells me why this error occurs?
0
0
935
Feb ’23
Reply to PKProduct Errors when delivering properly signed & validated package via MDM
posting the follow up... The error here is what I also interpreted as the error, but the actual error is up higher in the stack when streaming appstored logs. 2023-01-27 05:30:43.875108-0800 0x6092b Error 0x0 1252 0 appstored: [com.apple.appstored:AppInstall] [MNF16FC110D/16FC110D-D057-42B7-9F7B-6A283991A2D0] Could not create PKProduct: Error Domain=NSCocoaErrorDomain Code=4 The file Distribution doesn't exist. UserInfo={NSFilePath=Distribution} I switched the package from component to distribution and it solved my issue.
Feb ’23
Runtime error when using StoreKit 2
When performing StoreKit 2 operations in my Mac app, even very simple ones like AppStore.sync() a small but steady percentage of users experiences the following error: systemError(Error Domain=NSCocoaErrorDomain Code=4097 connection to service named com.apple.storekitagent UserInfo={NSDebugDescription=connection to service named com.apple.storekitagent}) Rebooting or re-downloading the App from the Mac App Store, as well as signing out and in again on the Mac App Store does not solve the issue. Strangely enough all of the affected users I'm aware of were initially able to perform In-App purchases via the said app. Without any updates or anything else however suddenly after a restart of the app the above error gets thrown by the system. As I have not found any way to solve this issue yet and the said customers are consequently left without service even though they are paying customers, I am desperate to find help with this issue. Given the simplicity of the AppStore.sync() method for example I can't i
2
0
1.7k
Jan ’23