SchimmelDevNest

Programming

Xcode 6 crashes on submitting Archive

27 September 2026 · 9 min read

Xcode 6 crashes on submitting Archive

Encountering an unexpected crash during the final stages of app deployment can be incredibly frustrating for any iOS developer. Specifically, the issue where Xcode 6 crashes on submitting Archive has been a notorious stumbling block for many, often appearing right when you’re ready to share your hard work with the world. This particular problem, prevalent during the transition phases of iOS development and Xcode versions, can halt your workflow and leave you searching for answers. While Xcode 6 is an older version, many legacy projects still rely on it, making this a relevant concern for maintaining existing applications. Understanding the common causes and implementing effective troubleshooting steps is crucial to overcome this hurdle and successfully submit your archive to the App Store.

Understanding the “Xcode 6 Crashes on Submitting Archive” Phenomenon

The specific challenge of Xcode 6 crashing during the archive submission process often stems from its particular environment and the iOS ecosystem it supported. Xcode 6 was primarily used for developing apps targeting iOS 8 and early iOS 9, a period when Apple was rapidly evolving its development tools and submission protocols. These crashes aren’t random; they usually point to underlying configuration issues or inconsistencies that Xcode’s validation process flags aggressively, sometimes leading to an abrupt termination rather than a clear error message.

Developers frequently report these crashes occurring after the archive has been successfully built and validated locally, but just as the “Submit to App Store” workflow initiates within the Xcode Organizer. This indicates that the problem typically lies within the final stages of handshake between your local development environment and Apple’s App Store Connect servers. It’s not uncommon for inconsistencies in provisioning profiles, code signing identities, or even subtle project build settings to trigger these critical failures. Identifying the precise moment of the crash and any preceding warnings can offer valuable clues.

The transition from older build systems to newer ones, even within Xcode 6’s lifecycle, could introduce subtle incompatibilities. For instance, an outdated developer certificate or a misconfigured app ID could lead to validation failures that manifest as a crash instead of a readable error. Many developers recall needing to meticulously check every detail of their project’s setup to pinpoint the exact cause of an Xcode 6 crashes on submitting Archive problem, a task that often felt like searching for a needle in a haystack without clear guidance from the IDE itself.

Diagnosing the Root Cause: Common Culprits

When Xcode 6 unexpectedly crashes during the archive submission, the culprit is often one of a few common issues related to how your app is built and prepared for distribution. These problems are frequently tied to code signing, provisioning profiles, or discrepancies in your project’s build settings. A robust understanding of these areas is paramount for effective diagnosis and resolution.

Code signing is a critical security measure that verifies your app comes from a trusted developer and hasn’t been tampered with. Issues here are a primary cause of Xcode 6 crashes on submitting Archive. This can include expired developer certificates, mismatched provisioning profiles (distribution vs. development), or incorrect bundle identifiers. Xcode needs to ensure that the archived build is signed with a valid distribution certificate and a corresponding distribution provisioning profile that matches the app’s bundle ID exactly. Any deviation can lead to validation failure and, in older Xcode versions, a crash.

Another frequent cause involves the build settings within your Xcode project. Sometimes, a project might have legacy settings that conflict with current App Store requirements, even for older apps. This could involve unsupported architectures, incorrect framework linking, or even pre-compiled headers that cause issues during the final validation process on Apple’s servers. Ensuring your project’s build settings are clean and optimized for distribution, with no lingering development-specific flags, is key.

Here are some common culprits to investigate when you face archive submission crashes:

  • Expired or Revoked Certificates: Ensure your Apple Developer Program membership is active and your distribution certificate is valid.
  • Mismatched Provisioning Profiles: The profile used for archiving must be a distribution profile, matching your app’s bundle ID and the distribution certificate.
  • Incorrect Bundle Identifier: The bundle ID in your project’s Info.plist must precisely match the one registered with your App ID in App Store Connect.
  • Build Setting Discrepancies: Check for any custom build settings that might interfere with the standard distribution process.
  • Old Toolchain/SDK Issues: While Xcode 6 is specific, ensure its internal components are not corrupted or outdated.

Step-by-Step Troubleshooting for Archive Submission Crashes

Resolving an Xcode 6 crashes on submitting Archive issue requires a methodical approach. By following a structured troubleshooting process, you can systematically eliminate potential causes and pinpoint the exact problem. This guide focuses on steps known to resolve many such issues in Xcode 6.

To troubleshoot and resolve archive submission crashes:

  1. **Verify Your Certificates and Provisioning Profiles:**Go to Apple Developer Account and check the status of your Distribution Certificates and associated Provisioning Profiles. Make sure they are active, not expired, and correctly configured for App Store distribution. If necessary, revoke and regenerate them, then download and install them into Xcode. Ensure the correct team is selected in Xcode’s General settings for your target.
  2. **Clean and Rebuild Your Project:**Sometimes, corrupted build artifacts can lead to submission issues. In Xcode, select “Product” > “Clean Build Folder” (⌥⇧⌘K). After cleaning, try building your archive again. This ensures that a fresh build is created, free from any old, potentially problematic compiled files.
  3. **Check Your Project’s Build Settings:**Navigate to your project’s build settings. Pay close attention to the “Code Signing Identity” and “Provisioning Profile” settings under the “Signing” section for your Release configuration. Ensure they are set to your Distribution Certificate and the correct Distribution Provisioning Profile. Also, verify that the “Architectures” and “Valid Architectures” are appropriate for your target devices and iOS version. For more on general project settings, consider reviewing this guide on Xcode project configuration.
  4. **Use Application Loader (if Xcode continues to crash):**If Xcode’s built-in submission process consistently crashes, you can often bypass it by using the Application Loader. First, create your archive in Xcode (Product > Archive). Then, in the Xcode Organizer, right-click on your archive and select “Show in Finder.” Right-click the .xcarchive file and select “Show Package Contents.” Inside, navigate to “Products” > “Applications,” where you’ll find your .app file. Compress this .app file into a .zip. Then, open Application Loader (usually found under Xcode > Open Developer Tool), sign in, and select “Deliver Your App.” Point it to your compressed .zip file. This separate tool is often more robust for handling the submission handshake and can provide more verbose error messages if issues persist.

When you encounter an Xcode 6 crashes on submitting Archive error, the most effective approach is often to simplify the submission process by using Application Loader. This separate utility allows for direct upload of your compiled application package, bypassing the potentially unstable parts of Xcode’s built-in submission interface. By exporting your archive from Xcode and then using Application Loader, you gain a more stable conduit to App Store Connect, often revealing clearer error messages that Xcode might have suppressed during a crash.

Best Practices to Prevent Future Archive Submission Issues

Preventing future occurrences of Xcode 6 crashes on submitting Archive requires adopting a disciplined approach to your development and distribution workflow. While Xcode 6 is an older environment, many of these best practices are timeless and apply to modern development as well, ensuring a smoother journey from development to deployment.

Regular maintenance of your developer account is paramount. This includes consistently monitoring the expiration dates of your distribution certificates and provisioning profiles. Apple provides ample warnings, but proactively renewing them before they expire can save significant headaches. Ensure that all team members use the same, Question & Answer :

Today I uploaded my first build of first app successfully to App Store for beta testing. After making a few changes, when I tried to submit the new archive again Xcode crashed, and still crashes.

It’s the log:

Process: Xcode [36810] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 6.3.2 (7718) Build Info: IDEFrameworks-7718000000000000~2 App Item ID: 497799835 App External ID: 812404257 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Xcode [36810] User ID: 501 Date/Time: 2015-06-17 21:59:26.432 +0430 OS Version: Mac OS X 10.10.3 (14D136) Report Version: 11 Anonymous UUID: A70B5585-6ADF-B647-C184-94420293DB9F Sleep/Wake UUID: 536542A5-38C8-405F-8A5E-28DBE775C033 Time Awake Since Boot: 110000 seconds Time Since Wake: 18000 seconds Crashed Thread: 14 Dispatch queue: NSOperationQueue 0x7fdb9771af00 :: NSOperation 0x7fdb97679160 (QOS: USER_INITIATED) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: ProductBuildVersion: 6D2105 ASSERTION FAILURE in /SourceCache/IDEFrameworks/IDEFrameworks-7718/IDEFoundation/Issues/IDEIssueManager.m:457 Details: This method must only be called on the main thread Object: <IDEIssueManager> Method: +_issueProviderInfo Thread: <NSThread: 0x7fdb971db920>{number = 80, name = (null)} Hints: None Backtrace: 0 0x0000000102e28b6a -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit) 1 0x0000000101b765df _DVTAssertionHandler (in DVTFoundation) 2 0x0000000101b768ce _DVTAssertionFailureHandler (in DVTFoundation) 3 0x00000001024f248e +[IDEIssueManager _issueProviderInfo] (in IDEFoundation) 4 0x00000001024f1b0d -[IDEIssueManager _updateIssueProviders] (in IDEFoundation) 5 0x0000000101b893de __73-[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:]_block_invoke (in DVTFoundation) 6 0x0000000101afed5c DVTInvokeWithStrongOwnership (in DVTFoundation) 7 0x00000001019b03e4 -[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:] (in DVTFoundation) 8 0x00007fff8a8af0f3 NSKeyValueNotifyObserver (in Foundation) 9 0x00007fff8a8bbd68 NSKeyValueDidChange (in Foundation) 10 0x00007fff8a87497d -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation) 11 0x00007fff8befddaf doSetValuesInSourceWithKVO (in CoreFoundation) 12 0x00007fff8befdc46 _CFXPreferencesReplaceValuesInNamedVolatileSource (in CoreFoundation) 13 0x00007fff8aa4b027 -[NSUserDefaults(NSUserDefaults) setVolatileDomain:forName:] (in Foundation) 14 0x0000000119e34a13 -[NSUserDefaults(ITunesConnectFoundationExtensions) REPLACEMENT_setVolatileDomain:forName:] (in ITunesConnectFoundation) 15 0x0000000119e34f87 -[NSUserDefaults(ITunesConnectFoundationExtensions) synchronizeRegistrationDomains] (in ITunesConnectFoundation) 16 0x0000000119e34d5d -[NSUserDefaults(ITunesConnectFoundationExtensions) registerPriorityDefaults:] (in ITunesConnectFoundation) 17 0x0000000119e2669e -[MZJSONServiceClient processApplicationSettings:] (in ITunesConnectFoundation) 18 0x0000000119e26d7d -[MZJSONServiceClient connectionDidFinishLoading:] (in ITunesConnectFoundation) 19 0x00007fff8846d24d __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke (in CFNetwork) 20 0x00007fff8846d0b1 -[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] (in CFNetwork) 21 0x00007fff8846cfb7 -[NSURLConnectionInternal _withActiveConnectionAndDelegate:] (in CFNetwork) 22 0x00007fff8846df74 ___ZN27URLConnectionClient_Classic26_delegate_didFinishLoadingEU13block_pointerFvvE_block_invoke (in CFNetwork) 23 0x00007fff88521703 ___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 (in CFNetwork) 24 0x00007fff883c2cec RunloopBlockContext::_invoke_block(void const*, void*) (in CFNetwork) 25 0x00007fff8bf0e664 CFArrayApplyFunction (in CoreFoundation) 26 0x00007fff883c2bad RunloopBlockContext::perform() (in CFNetwork) 27 0x00007fff883c2998 MultiplexerSource::perform() (in CFNetwork) 28 0x00007fff883c27ba MultiplexerSource::_perform(void*) (in CFNetwork) 29 0x00007fff8bf42a01 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (in CoreFoundation) 30 0x00007fff8bf34b8d __CFRunLoopDoSources0 (in CoreFoundation) 31 0x00007fff8bf341bf __CFRunLoopRun (in CoreFoundation) 32 0x00007fff8bf33bd8 CFRunLoopRunSpecific (in CoreFoundation) 33 0x00007fff8a8fda59 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] (in Foundation) 34 0x00007fff8a91bcce -[NSRunLoop(NSRunLoop) runUntilDate:] (in Foundation) 35 0x0000000119e25d00 -[MZJSONServiceClient getResultDictionary] (in ITunesConnectFoundation) 36 0x0000000119e28eb3 -[MZLabelServiceClient invokeSOAPCall] (in ITunesConnectFoundation) 37 0x0000000119e3097d -[MZWebServiceOperationWorker execute] (in ITunesConnectFoundation) 38 0x0000000119e30e11 -[MZWebServiceWorker run] (in ITunesConnectFoundation) 39 0x0000000119df854d -[MZWorkItem main] (in ITunesConnectFoundation) 40 0x00007fff8a8c6a6c -[__NSOperationInternal _start:] (in Foundation) 41 0x00007fff8a8c6543 __NSOQSchedule_f (in Foundation) 42 0x00007fff89468c13 _dispatch_client_callout (in libdispatch.dylib) 43 0x00007fff8946c365 _dispatch_queue_drain (in libdispatch.dylib) 44 0x00007fff8946decc _dispatch_queue_invoke (in libdispatch.dylib) 45 0x00007fff8946b6b7 _dispatch_root_queue_drain (in libdispatch.dylib) 46 0x00007fff89479fe4 _dispatch_worker_thread3 (in libdispatch.dylib) 47 0x00007fff86f91637 _pthread_wqthread (in libsystem_pthread.dylib) 48 0x00007fff86f8f40d start_wqthread (in libsystem_pthread.dylib)

Note: I can validate the Archive without error.

Will re-installing XCode help me to fix it?

Close any projects or workspace windows you have open in Xcode but leave Organizer window open and re-submit worked for me.