In developing a new MacOS app in Xcode I set up a Storekit configuration file so I could test 2 non-consumable purchases locally. I've been successfully testing them for the past couple of weeks, but suddenly yesterday I found I was unable to make purchases. I can successfully fetch products, but when I try to purchase either of them, I get the following error: Error handling payment sheet request: 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.} Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=5115 Received failure in response from Xcode UserInfo= {NSDebugDescription=Received failure in response from Xcode, NSUnderlyingError=0x600002d44ae0 {Error Domain=NSCocoaErrorDomain Code=4099 The connection to service created from an endpoint was invalidated from this process. UserInfo=
Search results for
NSCocoaErrorDomain
1,063 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hey all, I am facing a weird issue when exporting my multi platform project. The project does not make use of the multi platform targets of Xcode yet. For each module in the app there exists two targets, one for iOS and one for watchOS. Each of these targets link agains a binary framework that is imported via SPM. Building works fine but as soon as I want to archive the project at the last step it complains that the Signature for the third party binary framework already exists. Which I think is a valid error message, but it seems to be a bug that the archive process either: Does not override it, which would be reasonable Or it should distinguish between the platforms Or should just not create two signature and just have one signature file created The error message I see “ThirdParty.xcframework.signature” couldn’t be copied to “Signatures” because an item with the same name already exists. Domain: NSCocoaErrorDomain Code: 516 Failure Reason: A file with the name “ThirdParty.xcframework.signature” alre
Error handling payment sheet request: 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.} Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=5115 Received failure in response from Xcode UserInfo={NSDebugDescription=Received failure in response from Xcode, NSUnderlyingError=0x60000024d470 {Error Domain=NSCocoaErrorDomain Code=4099 The connection to service created from an endpoint was invalidated from this process. UserInfo={AMSDescription=An unknown error occurred. Please try again., AMSURL=http://localhost:50117/WebObjects/MZBuy.woa/wa/inAppBuy, NSDebugDescription=The connection to service created from an endpoint was invalidated from this process., AMSStatusCode=200, AMSServerPayload={ app-list = ( ); dialog = { cancelButtonString = Cancel; defaultButton = Buy; explanation = Do yo
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi there, we are developing an application using Firebase Messenging. Although everything runs smoothly when launching the application from Xcode to a dev iPhone (we can get FCM token and receive push notifications), we also get an AMFI issue when installing the application from Testflight : AMFI: constraint violation /private/var/containers/Bundle/Application/[...]/App.app/Frameworks/FirebaseCore.framework/FirebaseCore has entitlements but is not a main binary The application does not crash, but Firebase library is broken. 11.9.0 - [FirebaseMessaging][I-FCM023014] Error while reading embedded mobileprovision Error Domain=NSCocoaErrorDomain Code=260 The file “embedded.mobileprovision” couldn’t be opened because there is no such file. UserInfo={NSFilePath=/private/var/containers/Bundle/Application/[...]/App.app/embedded.mobileprovision, NSURL=file:///private/var/containers/Bundle/Application/[...]/App.app/embedded.mobileprovision, NSUnderlyingError=0x3007cde00 {Error Domain=NSPOSIXErrorDomain Code=2 N
Topic:
App & System Services
SubTopic:
General
Tags:
Background: I've used Xcode 11.3 for years with my 2015 macbook pro running OS 10.14.6. About a week ago, I thought I had to solve a problem by updating OS. Under that OS, 12.x, I installed the newest Xcode. This ended up not being the right solution, and caused other issues, so I switched back to 10.14.6. After the switch-back, I had to also delete that newer Xcode, and re-download Xcode 11.3. Now, it will not open at all, and I get a popup that says Loading a plug-in failed The plug-in or one of its prerequisite plug-ins may be missing or damaged and may need to be reinstalled. I try opening via Terminal and this is the printout: $ /Applications/Xcode.app/Contents/MacOS/Xcode ; exit; then some warnings that I suspect are not the problem, then the errors: 2022-11-12 19:58:27.335 Xcode[1562:20866] [MT] DVTPlugInLoading: Failed to load code for plug-in com.apple.dt.dbg.DebuggerFoundation (/Applications/Xcode.app/Contents/PlugIns/DebuggerFoundation.ideplugin), error = Error Domain=NSCocoaErrorDomain Co
So I was running Xcode 12 fine. My company put Cylance on my laptop. I think forgot I had it running and installed Xcode 13 beta. Cylance flagged a few files - DeviceLink stuff. I launched the beta - I got the loading a plug-in error dialog. Okay I thought, just throw it out - my regular Xcode 12 should be fine. I launch it - same dialog. Uh oh... this is my work laptop and I just lost the ability to use Xcode?? I throw out Xcode 12 and get it again from the Mac AppStore. After forever installing, the same thing. I do not know how to fix this. I launched Xcode from the Terminal and here is the output: 2021-06-15 12:41:54.415 Xcode[23284:313303] [MT] DVTPlugInLoading: Failed to load code for plug-in com.apple.dt.IDE.IDEiOSSupportCore (/Applications/Xcode.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin), error = Error Domain=NSCocoaErrorDomain Code=3587 dlopen_preflight(/Applications/Xcode.app/Contents/PlugIns/IDEiOSSupportCore.ideplugin/Contents/MacOS/IDEiOSSupportCore): Library not loaded: /System/L
I'm building a UIKit app that reads user's Apple Music library and displays it. In MusicKit there is the Artwork structure which I need to use to display artwork images in the app. Since I'm not using SwiftUI I cannot use the ArtworkImage view that is recommended way of displaying those images but the Artwork structure has a method that returns url for the image which can be used to read the image. The way I have it setup is really simple: extension MusicKit.Song { func imageURL(for cgSize: CGSize) -> URL? { return artwork?.url( width: Int(cgSize.width), height: Int(cgSize.height) ) } func localImage(for cgSize: CGSize) -> UIImage? { guard let url = imageURL(for: cgSize), url.scheme == musicKit, let data = try? Data(contentsOf: url) else { return nil } return .init(data: data) } } Now, everytime I access .artwork property (so a lot of times) the main thread gets blocked and the console output gets bombared with messages like these: 2023-07-26 11:49:47.317195+0200 Plum[998:297199] [Artwork] Failed to cre
Dear Apple & Community, I am encountering an issue while running my Unit tests on Xcode 16. I'm receiving the following error in the debugger area. 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 .....
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
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Thanks for providing the project and steps. I tried them with my iPhone 16 Plus + iOS 18.4 beta 2 (22E5216h), and reproduced the issue. Other than the error message you described, I saw other errors happening at the earlier stage. For the reference of other folks, I pasted the messages here: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _performSetupRequest:]_block_invoke(1246): : Failed to set up CloudKit integration for store: (URL: file:///var/mobile/Containers/Data/Application/C3C44E20-5618-4837-BB14-21CFF9E45799/Library/Application%20Support/default.store) Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={NSLocalizedFailureReason=The mirroring delegate could not initialize because it's store was removed from the coordinator.} ... BUG IN CLIENT OF CLOUDKIT: Registering a handler for a CKScheduler activity identifier that has already been registered (com.apple.coredata.cloudkit.activity.export.E2260BCD-9E87-4C0E-B3F3-68CA9843D246). CoreData+CloudKit: -[NSCloudKi
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
I am using NSPersistentCloudKitContainer and I decided to add a property to an entity. I accidentally ran try! container.initializeCloudKitSchema(options: []) while using the production container in Xcode (com.apple.developer.icloud-container-environment) which throw a couple of errors and created some FAKE_ records in my production container. So I changed to my development container and ran the try! container.initializeCloudKitSchema(options: []) and now it succeeded. After that I cleaned up the FAKE_ records scattered in production container but in Xcode when I'm running I now get these logs in the console (and I can't seem to get rid of them): error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _importFinishedWithResult:importer:](1398): : Import failed with error: Error Domain=NSCocoaErrorDomain Code=4864 *** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: incomprehensible archive (0x53, 0x6f, 0x6d, 0x65, 0x20, 0x73, 0x61, 0x6d) UserInfo={NSDebugDescription=*** -[NS
Hello. See the code below. struct ContentView: View { var body: some View { TabView { VehicleTab() .tabItem({ Label(Vehicles, systemImage: car.fill)}) .modelContainer(for: Vehicle.self) TransactionsTab() .tabItem { Label(Transactions, systemImage: dollarsign) } .modelContainer(for: Transaction.self) } } } Using the .modelContainer() in this way seems to be causing some issue. I was under the assumption that this would just create a container for each view. I get the error below in this configuration. If I comment out either one of the .modelContainer() modifiers, it works fine. Query encountered an error: Error Domain=NSCocoaErrorDomain Code=256 The file “default.store” couldn’t be opened. Are you not able to do what I'm doing? Is there a way to have two separate containers?
Hello, I'm a newer Xcode developer trying to debug an error I'm getting in my iOS app. I'm using this code to get file content: //inputFile = here is my file name with no extension let filepath = Bundle.main.path(forResource: inputFile, ofType: txt) //filepath = /Users/username/Library/Developer/CoreSimulator/Devices/[DeviceGUID]/data/Containers/Bundle/Application/[AppGUID]/AppName.app/here is my file name with no extension.txt let fileContent = try String(contentsOfFile: filepath) That line generates a runtime error: error NSError domain: NSCocoaErrorDomain - code: 264 0x0000600000c74d20 Xcode 16.2 on macOS Sequoia 15.1.1 I had this code working... I had to step away from the code for a few months; I updated Xcode and now I'm getting this error. (I could've screwed the code up). I navigated to the directory and the file is there. Anybody have any ideas? Thank you! Hoss
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?
After the release of StoreKit 2.0, the in-app purchase failure rate increased by 63.19%, with the majority of errors being StoreKitError.unknown. When encountering this error, many users repeatedly attempt to make a purchase, but the outcome remains unchanged, resulting in the same unknown error. In some cases, users who wait approximately 2 minutes before retrying the purchase may either succeed or encounter the following error: “StoreKit.StoreKitError.systemError(Error Domain=NSCocoaErrorDomain Code=4097 connection to service named com.apple.storekitd”)”. This issue has directly impacted our app's purchasing flow. Because our app only displays the promotional purchase offer once, these issues have significantly reduced the number of users successfully completing the offer. As a result, the conversion rate for this promotion has dropped well below expectations, negatively impacting our business metrics.