I'm looking at logs for EAUpdaterService to see why my new pair of AirPods Max will not update from firmware 3C16. I see that the firmware is being recognized as out of date, and the new version is being downloaded. It appears that, in the process of starting the actual update, the connection is invalidated, and I'm not sure why, or what to do about it: EAUpdaterService error = Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 159 - Sandbox restriction.}
Search results for
NSCocoaErrorDomain
1,063 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am trying to build a very basic app using Core Data and CloudKit. I am logged into my CloudKit account on my Mac, and I followed the instructions to run the sample project that Apple provided on their website.Using the sample project as a guide, I tried to build a simpler app using the instructions provided here.However, after building trying to run my sample project, I get the following error stack trace in my console:CoreData: debug: CoreData+CloudKit: -[PFCloudKitOptionsValidator validateOptions:andStoreOptions:error:](35): Validating options: <NSCloudKitMirroringDelegateOptions: 0x60000097f960> containerIdentifier:iCloud.com.cybermedia.CloudKitTest1 initializeSchema:YES ckAssetThresholdBytes:<null> operationMemoryThresholdBytes:<null> useEncryptedStorage:NO automaticallyDownloadFileBackedFutures:NO automaticallyScheduleImportAndExportOperations:YES skipCloudKitSetup:NO preserveLegacyRecordMetadataBehavior:NO useDaemon:YES apsConnectionMachServiceName:<null> containerProvider:<
Hi.In the latest betas I am having difficulty using the new CoreSpotlight API to index my app's content.[[CSSearchableIndex defaultSearchableIndex] indexSearchableItems:newItemsToIndex completionHandler:^(NSError *indexError) {...}];After calling this method, I get several messages in the debugger that read:[com.apple.corespotlight.log.index] Error caught while talking to the index agent, index:<CSSearchableIndex:0x7fc02d98be90; name=CSSearchableIndexShared>, error:Error Domain=NSCocoaErrorDomain Code=4097 Couldn’t communicate with a helper application. (connection to service named com.apple.spotlight.IndexAgent) UserInfo=0x7fc02da64fc0 {NSDebugDescription=connection to service named com.apple.spotlight.IndexAgent}As far as the release notes detail, there are no known issues with the API. Is anyone else having this issue?
Following the advice here: https://developer.apple.com/documentation/gamekit/enabling_and_configuring_game_center I tried allowing incoming connections in addition to outgoing connections but it doesn't help. I get this error: Could not get services from gamed. Please file a radar including GameKit logs, and any gamed crash logs. ERROR Error Domain=NSCocoaErrorDomain Code=4099 The connection to service named com.apple.gamed was invalidated: failed at lookup with error 159 - Sandbox restriction. UserInfo={NSDebugDescription=The connection to service named com.apple.gamed was invalidated: failed at lookup with error 159 - Sandbox restriction.} This happens on macOS 12.6.1. What am I doing wrong? Is there a workaround?
Does a core data database location have to be under the app's applicationDocumentsDirectory? That is how it is behaving for me.I would like to create my core data database in a folder of my choosing; however, when I attempt to create it outside of the applicationDocumentsDirectory, it fails.Works fine:databaseURL path: Users/rickschlueter/Library/Containers/com.eBetsy.eBetsy/Data/Library/Application%20Support[coordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:self.storeDataURL options:options error:&error]Fails:databaseURL path : Users/rickschlueter/Pictures/Inventory%20Databaseerror: Error Domain=NSCocoaErrorDomain Code=512 The file couldn’t be saved. UserInfo={reason=Failed to create file; code = 1}
My app has suddenly stopped serving on demand resources from test flight and was rejected I submitted the app due to on demand resources being unavailable.It works locally. I am not hosting on demand resources, I am using Apple hosted resources.The full error message is NSCocoaErrorDomain = 4994 The requested application data doesn't exist.UserInfo=(NSLocalizedFailureReason=Request could not be completed. Invalid tag set in '{(tag1, tag2)}.tag1 and tag2 exist in Target->Resource TagsWhen I look in itunesConnect->Activity->IOS Builds->Version I can see that the app has the correct number of asset packs.Any ideas?
I am using below piece of code to delete a fileif FileManager.default.fileExists(atPath: Path) { do { try FileManager.default.removeItem(atPath: Path) } catch { print(error) } }Path is /Library/LaunchAgents/com.example.agent.plistI am getting below errorError Domain=NSCocoaErrorDomain Code=513 “com.example.agent.plist” couldn’t be removed because you don’t have permission to access it. UserInfo={NSFilePath=/Library/LaunchAgents/com.example.agent.plist, NSUserStringVariant=( Remove), NSUnderlyingError=0x600000c76af0 {Error Domain=NSPOSIXErrorDomain Code=13 Permission denied}}How can i delete a file with admininistrative priveleges from swift. Is there a way i can do without involving apple scripts and shell scripts using native swift?
I've got a trivial MacOS script:#!/bin/sh # OpenInSafari.sh open /tmp/GitNAVs.htmlthat I try to invoke with:let bundle = Bundle.main if let script = bundle.url(forResource: OpenInSafari, withExtension: sh) { do { let scriptTask = try NSUserScriptTask(url: script) scriptTask.execute(completionHandler: nil) } catch { print(error) }But I get:Error Domain=NSCocoaErrorDomain Code=259 The file “OpenInSafari.sh” couldn’t be opened because it isn’t in the correct format.The *.sh file was created by Xcode and is where it's supposed to be in the bundle with read and write permissions. Any clue what's the problem?Thanks,Richard
For using today extension, I override default directory with app group. class NSCustomPersistentContainer: NSPersistentContainer { override open class func defaultDirectoryURL() -> URL { var storeURL = FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: group.YourApp) storeURL = storeURL?.appendingPathComponent(YourApp.sqlite) return storeURL! } } it's working fine : on my widget I could retrieve my Coredata information... BUT I've notice that an error appear on the first time I install my app returned error NSCocoaErrorDomain(512) with userInfo dictionary { reason = Failed to create file; code = 2; it's not crashing app and could use Coredata but could you tell me how why this error on debug? thanx a lot
I have a swift application and there is a requirement to download mp4 files from AWS bucket. I'm able to download file with smaller sizes but can't download files above particular sizes say 2GB and its depend on device too. While trying to download such kind of files, getting the below error `Failed with error: Error Domain=NSCocoaErrorDomain Code=256 The file couldn’t be opened. Also noticed that when trying to download 140 files with size of 100 MB each only able to download a maximum of approximately 100 files, after that I got the same error. Is there any such limit on iOS for downloading files.
I am trying to migrate my Core Data model to a new version with a new attribute added to it. Since my app supports macOS 13 I am not able to use the newly introduced Staged migrations. After much digging I found that the app is not able to find the Mapping Model when one of the attribute has Preserve after deletion enabled. I have enabled migration debbuging using com.apple.CoreData.MigrationDebug 1 I am getting following error error: CoreData: error: (migration) migration failed with error Error Domain=NSCocoaErrorDomain Code=134140 Persistent store migration failed, missing mapping model. What is the way out here?
I was able to reproduce the bug by transferring from Korean Windows 10 using iTunes.Thanks to musebook for the information about reproducing the bug.I've created txt files from Windows, Mac and transferred using Windows iTunes and Mac iTunes. I also created a file directly from iOS.Here's the array returned from [[NSFileManager defaultManager] contentsOfDirectoryAtPath:path error:&error]; Mac U1112U1161U11abU1100U1173U11af.txt, Windows Ud55cUae00.txt, iOS U1112U1161U11abU1100U1173U11af.txtAll files have same 'Hangul Korean 2 letters with prefix where they came from. Mac and iOS share the same Unicode and file from Windows have different Unicode. When I NSLog each NSString from the array, I could see correct Korean output. I also see all files from iTunes file sharing correctly both from Windows and Mac.When doing attributesOfItemAtPath with: NSString *filepath = [path stringByAppendingPathComponent:filename]; NSDictionary *dict=[fileManager attributesOfItemAtPath:filepath error:&error];The Windows <
Topic:
Accessibility & Inclusion
SubTopic:
General
Tags:
Thanks for your reply... Here is the information you have requested: Request xcrun devicectl list preferredDDI Response Host CoreDevice version: 397.21 The DDI used for the iOS platform: • hostDDI: file:///Library/Developer/DeveloperDiskImages/iOS_DDI.dmg ▿ ddiMetadata: • buildUpdate: 16A242d • contentIsCompatible: true • coreDeviceVersionChecksIncludeDevelopmentRevision: true • developmentRevision: 0 • enforcingCoreDeviceVersionChecks: true • platform: iOS ▿ projectMetadata: • Citrine-94 • CoreDevice-397.21 • DTDeveloperDiskImageSupport-14.0.0 • DTOCMock-23002 • GPUToolsDevice_DDI-300.21 • JetsamProperties-2205 • LiveExecutionResultsLogger-20002 • Mercury-54 • XCTest-23196 • isUsable: true • variant: external The DDI used for the tvOS platform: • hostDDI: file:///Library/Developer/DeveloperDiskImages/tvOS_DDI.dmg ▿ ddiMetadata: • buildUpdate: 16A242d • contentIsCompatible: true • coreDeviceVersionChecksIncludeDevelopmentRevision: true • developmentRevision: 0 • enforcingCoreDeviceVersionChecks: true • platfo
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
how to use CFBundleAlternateIcons ?in my info.plist: <key>CFBundleIcons</key> <dict> <key>CFBundlePrimaryIcon</key> <dict> <key>CFBundleIconFiles</key> <array> <string>Doodad.icns</string> </array> </dict> <key>CFBundleAlternateIcons</key> <dict> <key>CFBundleIconFiles</key> <array> <string>logo29x29</string> <string>logo40x40</string> <string>logo60x60</string> </array> </dict> </dict>in my code : UIApplication *app = [UIApplication sharedApplication]; BOOL reuslt = app.supportsAlternateIcons; NSLog(@%zd,reuslt); [app setAlternateIconName:@logo completionHandler:^(NSError * error) { NSLog(@%@,error); }]; [app setAlternateIconName:@logo29x29 completionHandler:^(NSError * error) { NSLog(@%@,error); }]; [app setAlternateIconName:@logo29x29@2x.png completionHandler:^(NSError * error) { NSLog(@%@,error); }]; NSLog(@name=%@,app.alternateIconName);ou
Hi there,Our users are experiencing crashes in the App Kit code when NSDocumentController is trying to reopen a document that the user has no longer access to.Not sure how that happens in the wild, might be just another OS bug, however it's easy to replicate with some chown/chmod magic..Is there a way to handle this error or display it to the user?At the moment it's only displayed on the Console - which neither points the user to the cause of the issue nor gives our app any way to intercept and prevent App Kit from crashing.The NSDocumentController method causing the problem/console output is:2017-02-18 06:15:56.838164 My App [6036:900355] -[NSDocumentController reopenDocumentForURL:withContentsOfURL:display:completionHandler:] failed during state restoration. Here's the error:Error Domain=NSCocoaErrorDomain Code=257 The autosaved document “test.layout” could not be reopened. You don’t have permission. UserInfo={NSLocalizedFailureReason=You don’t have permission., NSLocalizedDescription=The autosaved