Search results for

NSCocoaErrorDomain

1,063 results found

Post

Replies

Boosts

Views

Activity

Reply to SwiftData - Context missing for optional
I also tried changing the method of deletion to the following. This tries to delete entity Object that has a to-many relationship children: [Child]. guard let id = object.id else { return } do { try container.mainContext.delete(model: Object.self, where: #Predicate { object in object.id == id }) } catch { print(error) } This does not crash the app, but fails to delete the entity with the following console output: Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={Reason=Entity named:Object not found for relationship named:children, MissingEntity=Object. () ... I'm not sure what this means, perhaps someone more clever will find it useful. @DTS Engineer
Aug ’24
setCodeSigningRequirement and Security Agent Plugins
I have a security agent plugin that uses NSXPCConnection to communicate with a launch daemon. This works well, but I want to make sure the launch daemon has not been compromised. I added code to call setCodeSigningRequirement in my module that handles the client side of the NSXPCConnection. However, when used in the security agent plugin, remoteObjectProxyWithErrorHandler reports an error NSCocoaErrorDomain Code=4102 The code signature requirement failed. If I call my xpc module from a test application, I do not receive an error and everything works as expected. I have tried different code signing requirements. Even with just anchor apple generic I still get the error. The console log shows two entries of interest com.apple.SecurityAgentHelper.arm64 default 09:13:29.677567-0500 SecurityAgentHelper-arm64 EOGSecurityServiceClient biometricAuthorization remote proxy error: Error Domain=NSCocoaErrorDomain Code=4102 The code signature requirement failed. UserInfo={NSDebugDescription=The code sign
4
0
965
Aug ’24
Reply to setCodeSigningRequirement and Security Agent Plugins
More log details: com.apple.securityd debug 09:13:29.674468-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network default: NO com.apple.securityd debug 09:13:29.674577-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network blocked: YES com.apple.securityd debug 09:13:29.674621-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network blocked: YES com.apple.securityd debug 09:13:29.674952-0500 SecurityAgentHelper-arm64 staticCode SecStaticCode network blocked: YES com.apple.securityd debug 09:13:29.675103-0500 SecurityAgentHelper-arm64 xpc no query dict to determine whether for system keychain: Error Domain=NSOSStatusErrorDomain Code=-50 no object for key query (paramErr: error in user parameter list) UserInfo={numberOfErrorsDeep=0, NSDescription=no object for key query} com.apple.securityd default 09:13:29.675178-0500 SecurityAgentHelper-arm64 SecCritical Failed to talk to trustd after 4 attempts. com.apple.securityd debug 09:13:29.675329-0500 SecurityAgentHelper-arm64 xpc no query di
Topic: Code Signing SubTopic: General Tags:
Aug ’24
Reply to SwiftData unversioned migration
Ok Great! I have created my VersionedSchemas that define my four models and included them in the models property. And created my ModelContainer using the schema initializer Schema(versionedSchema: SchemaV2.self) Yet nothing works. I'm getting a few errors including: error: Attempting to retrieve an NSManagedObjectModel version checksum while the model is still editable. This may result in an unstable verison checksum. Add model to NSPersistentStoreCoordinator and try again. and error: Store failed to load. (type: SQLite, url: with error = Error Domain=NSCocoaErrorDomain Code=134504 Cannot use staged migration with an unknown model version. UserInfo={NSLocalizedDescription=Cannot use staged migration with an unknown model version.} with userInfo { NSLocalizedDescription = Cannot use staged migration with an unknown model version.; } I’m concerned that I may have corrupted my database with all the things I’ve been trying. Is there a chance that the database is corrupted, or is there something fundame
Aug ’24
SwiftUI/SwiftData view deep in the hierarchy looses model container
iPad mini device with iPadOS 17.4.1. I get this failure on iPad mini device exclusively. I have universal app and I doesn't get this error neither on iPhone or any simulator or macOS. I tried to reset the iPad, still getting the error. The error happens when I send the app to background from the particular app screen. Here is the error: error: Store failed to load. (type: SQLite, url: file:///dev/null) with error = Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={NSLocalizedFailureReason=The configuration named 'default' does not contain any entities.} with userInfo { NSLocalizedFailureReason = The configuration named 'default' does not contain any entities.; } What error says is that it loaded the store from file:///dev/null, which is wrong. Basically it looses the model container which is added via modelContaner modificator to the root view. The error get caused particularly by the @Environment(.modelContext) private var modelContext call in the view on which the f
4
0
1.1k
Aug ’24
Reply to Error Domain=NSCocoaErrorDomain Code=4099
same for me using google maps foe iOS. maybe a google issue, Burt for sure apple does not help finding what. Google Maps SDK for iOS version: 8.4.0.0 Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process. UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
Aug ’24
Error Domain=NSCocoaErrorDomain Code=4099
OS Version: macOS Sonoma 14.2 Xcode Version: 15.0 Im getting this log errors while launching my app: Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process. UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.} Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process. UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.} Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.commcent
2
0
5.9k
Aug ’24
Reply to After creating an hardlink sandboxed app cannot write to it anymore
I'm developing an application that uses hardlinks to track certain files created by the app. Initially, before the hardlink is created, the files behave as expected. For example, if the app generates a .number file, I can open and edit it with Numbers without any issues. However, once the hardlink is created, the file appears locked, and Numbers can no longer write to it. What are you actually trying to do here and why are hardlinks important here? The problem here is, setting the immediate issue aside, I'm not sure this will actually work very well in practice. Two problems I see off the top of my head: The standard safe save architecture works by having apps modify a copy of the file, the (ideally, atomically) exchange the new file with the old file. On file system that specifically this atomic operation (APFS and HFS+), I think that your hard link will still work. However, on all other file systems your hardlink will fail (as the new file is in fact a new file). In addition, I don't know what will happen i
Topic: App & System Services SubTopic: General Tags:
Aug ’24
Can't share Video to Facebook
I have the Facebook SDK version 17.0.2 and xcode 15. Sharing photos and links work fine but when I try sharing videos, I get the following error: Failed to log access with error: access= accessor:<> identifier:A9159DCD-76B1-4C77-A01E-DA611929B50B kind:intervalEvent timestampAdjustment:0 visibilityState:0 assetIdentifierCount:0 accessCount:0 tccService:kTCCServicePhotos, error=Error Domain=NSCocoaErrorDomain Code=4097 connection to service with pid 15679 named com.apple.privacyaccountingd UserInfo={NSDebugDescription=connection to service with pid 15679 named com.apple.privacyaccountingd}
1
0
532
Aug ’24
Crash when accessing Core Data because file couldn't be opened
We have a crash regarding to Core Data access that was not reproducible in our side but the crash count keeps increasing with the last stack trace is assertionFailure from Apple internal SDK. The last stack trace before the assertionFailure by system is our code initializing CoreData in DataContainer.init(name:bundle:inMemory:) where we will try to access CoreData and the error message we found from our 3rd party crash reporter is something like this DataStore/DataContainer.swift:30: Fatal error: Unresolved error Error Domain=NSCocoaErrorDomain Code=256 The file “Content.sqlite” couldn’t be opened. UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/9DBF262C-851A-486B-90CC-4397A8896525/Library/Application Support/Content.sqlite, NSSQLiteErrorDomain=13}, [NSSQLiteErrorDomain: 13, NSFilePath: /var/mobile/Containers/Data/Application/9DBF262C-851A-486B-90CC-4397A8896525/Library/Application Support/Content.sqlite] That sqlite file is supposed to be file used by Core Data (since we have no other c
1
0
1k
Aug ’24
SwiftData saying CoreData: error: Failed to stat path
This just started happening when installing my app on my phone and ipad. It still seems to work and the errors go away on the second installation, but it doesn't strike me as good. The app has not been released yet. When I remove the AppGroup, the error disappears. But I have a widget, so I need the AppGroup. I've cleaned the build, deleted derived files, and rebooted many times. I've deleted the app on the device and rebooted the device many times. I've deleted the AppGroup in iCloud and then recreated it. I was really hoping that would work, but nope. I've created a new App Group and that didn't make a difference either. So I'm stumped. Any thoughts on how to fix this? thanks CoreData: error: Failed to stat path '/private/var/mobile/Containers/Shared/AppGroup/2602E28B-089C-4011-BA09-19D11183E4F7/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
1
0
1.7k
Aug ’24
SwiftData: Unable to find a configuration named 'default' in the specified managed object model
I have a SwiftUI + SwiftData (with iCloud) app. The setup code is standard, with schema migrations (mostly lightweight, one custom). Everything works correctly except in one scenario. When I run a newer version of the app (with an updated schema adding one field + migration) on a device with the previous data container (the usual app version update through TestFlight), I encounter an issue on the first launch. The app crashes on the first cold start but runs successfully on subsequent launches. The error I receive on the first run is: addPersistentStoreWithType:configuration:URL:options:error: returned error NSCocoaErrorDomain (134060) NSLocalizedFailureReason : Unable to find a configuration named 'default' in the specified managed object model. What might be a problem and how to resolve it?
2
0
711
Aug ’24
Apple Pay Setup Issue for Native macOS App
Hi there, We're experiencing difficulties setting up Apple Pay for our native macOS app written in Swift. The main issue seems to be with the Apple Pay Merchant Identity configuration. When setting up the Merchant ID on the Apple Developer portal (https://developer.apple.com/account/resources/certificates/list), the only available platform listed is iOS. There's no option for us to add macOS to the supported platforms. Our app uses PKPaymentAuthorizationController to present the Apple Pay sheet, but it fails immediately with a Payment Not Completed error. The macOS Console.app shows: com.apple.PassKit.PaymentAuthorizationUIExtension - Payment failed with fatal error PKPeerPaymentService XPC Error: Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.passd.peer-payment was invalidated: failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.passd.peer-payment was invalidated: failed at lookup with err
6
0
1.1k
Jul ’24
Reply to Support semantic search with Core Spotlight
Tried to implement sample code from session 10131. Running on simulator gives me model loading errors: [Model loading] model loading failed with err -1000 for model path /Users/deszip/Library/Developer/CoreSimulator/Devices/EB928B2D-426F-40DD-A85F-7FF41442C02A/data/Containers/Data/Application/2DC7FE09-4F6E-411F-89CF-E65338EA2101/Library/Spotlight/Resources_V3/Experimental/models/spotlight_l2.mlmodelc and directives path /Users/deszip/Library/Developer/CoreSimulator/Devices/EB928B2D-426F-40DD-A85F-7FF41442C02A/data/Containers/Data/Application/2DC7FE09-4F6E-411F-89CF-E65338EA2101/Library/Spotlight/Resources_V3/Experimental/directives/directives_l2.mdplist And on device looks like smth wrong with xpc to some helper app: ### qid=2 error Error Domain=NSCocoaErrorDomain Code=4097 Couldn’t communicate with a helper application. reply: In general it just does not work :( Any hints or help appreciated.
Topic: App & System Services SubTopic: General Tags:
Jul ’24