Xcode 6 crashes when validating or submitting app archive

Question

This worked fine 2 days ago using the exact same archive and provisioning profile (selected from the organizer). Anyone else seeing this? I haven't updated Xcode, so it seems like it might be something on Apple's end causing a failure?

Application Specific Information:
ProductBuildVersion: 6A313
ASSERTION FAILURE in /SourceCache/IDEFrameworks/IDEFrameworks-6299/IDEFoundation/Issues/IDEIssueManager.m:457
Details:  This method must only be called on the main thread
Object:   <IDEIssueManager>
Method:   +_issueProviderInfo
Thread:   <NSThread: 0x7fa1abfa8e60>{name = (null), num = 44}
Hints:   None
Backtrace:
  0  0x00000001027adf0a -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit)
  1  0x000000010156dbaf _DVTAssertionHandler (in DVTFoundation)
  2  0x000000010156de9e _DVTAssertionFailureHandler (in DVTFoundation)
  3  0x0000000101ea2bce +[IDEIssueManager _issueProviderInfo] (in IDEFoundation)
  4  0x0000000101ea224d -[IDEIssueManager _updateIssueProviders] (in IDEFoundation)
  5  0x000000010157ffbe __73-[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:]_block_invoke (in DVTFoundation)
  6  0x00000001014fa6c8 DVTInvokeWithStrongOwnership (in DVTFoundation)
  7  0x00000001013ae124 -[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:] (in DVTFoundation)
  8  0x00007fff8aed8f28 NSKeyValueNotifyObserver (in Foundation)
  9  0x00007fff8aed80f8 NSKeyValueDidChange (in Foundation)
 10  0x00007fff8aedcbe6 -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)
 11  0x00007fff8ddf3f6f doSetValuesInSourceWithKVO (in CoreFoundation)
 12  0x00007fff8ddf3e0f _CFXPreferencesReplaceValuesInNamedVolatileSource (in CoreFoundation)
 13  0x00007fff8b07fafc -[NSUserDefaults(NSUserDefaults) setVolatileDomain:forName:] (in Foundation)
 14  0x00000001124ad9e9 -[NSUserDefaults(ITunesConnectFoundationExtensions) REPLACEMENT_setVolatileDomain:forName:] (in ITunesConnectFoundation)
 15  0x00000001124a3fac -[MZJSONServiceClient connectionDidFinishLoading:] (in ITunesConnectFoundation)
 16  0x00007fff8af877fd __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke (in Foundation)
 17  0x00007fff8af8772d -[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] (in Foundation)
 18  0x00007fff8af8761c -[NSURLConnectionInternal _withActiveConnectionAndDelegate:] (in Foundation)
 19  0x00007fff989e9284 ___ZN27URLConnectionClient_Classic26_delegate_didFinishLoadingEU13block_pointerFvvE_block_invoke (in CFNetwork)
 20  0x00007fff98a9f820 ___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 (in CFNetwork)
 21  0x00007fff989cc2ec ___ZNK17CoreSchedulingSet13_performAsyncEPKcU13block_pointerFvvE_block_invoke (in CFNetwork)
 22  0x00007fff8de04a94 CFArrayApplyFunction (in CoreFoundation)
 23  0x00007fff989cc1cb RunloopBlockContext::perform() (in CFNetwork)
 24  0x00007fff989cc073 MultiplexerSource::perform() (in CFNetwork)
 25  0x00007fff989cbea2 MultiplexerSource::_perform(void*) (in CFNetwork)
 26  0x00007fff8de395b1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (in CoreFoundation)
 27  0x00007fff8de2ac62 __CFRunLoopDoSources0 (in CoreFoundation)
 28  0x00007fff8de2a3ef __CFRunLoopRun (in CoreFoundation)
 29  0x00007fff8de29e75 CFRunLoopRunSpecific (in CoreFoundation)
 30  0x00007fff8af38adc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] (in Foundation)
 31  0x00007fff8af8110b -[NSRunLoop(NSRunLoop) runUntilDate:] (in Foundation)
 32  0x00000001124a3468 -[MZJSONServiceClient getResultDictionary] (in ITunesConnectFoundation)
 33  0x00000001124a55da -[MZLabelServiceClient invokeSOAPCall] (in ITunesConnectFoundation)
 34  0x00000001124aa904 -[MZWebServiceOperationWorker execute] (in ITunesConnectFoundation)
 35  0x00000001124aac02 -[MZWebServiceWorker run] (in ITunesConnectFoundation)
 36  0x000000011248336c -[MZWorkItem main] (in ITunesConnectFoundation)
 37  0x00007fff8aed78a1 -[__NSOperationInternal _start:] (in Foundation)
 38  0x00007fff8aed754b __NSOQSchedule_f (in Foundation)
 39  0x00007fff96f8528d _dispatch_client_callout (in libdispatch.dylib)
 40  0x00007fff96f897e3 _dispatch_async_redirect_invoke (in libdispatch.dylib)
 41  0x00007fff96f8528d _dispatch_client_callout (in libdispatch.dylib)
 42  0x00007fff96f87082 _dispatch_root_queue_drain (in libdispatch.dylib)
 43  0x00007fff96f88177 _dispatch_worker_thread2 (in libdispatch.dylib)
 44  0x00007fff934d0ef8 _pthread_wqthread (in libsystem_pthread.dylib)
 45  0x00007fff934d3fb9 start_wqthread (in libsystem_pthread.dylib)

Answer 1

Make sure you've accepted all of the new agreements in the Member Center.

To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh using the little button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.

On the other hand, the Organizer will just crash instead of warning you about un-signed agreements.

Answer 2

I solved the problem by:

1. Export the ipa in organiser
2. Using Application Loader to load the ipa to app store

Answer 3

I found solution/workaround on https://devforums.apple.com/ . Post by 優 Yu:

"Open the Organizer by performing Arches. Please close the only xcode body. Please do not close the Organizer screen. Please go and Submit Validation in that state. I'm glad If we can help you."

Works for me, but after validation I got strange message:

"The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.".

I ignored it and successfully submitted app to App Store. Looks like Apple broke their validation system, because I submitted an app 5 days ago without any problems.

Answer 4

是的，看起来苹果刚刚撤回了使用XCode 6上传的选项。使用XCode 5.1.1或Applauncher 2.9.1

Answer 5

只需在developer.apple.com的会员中心接受新的许可和协议即可。

Answer 6

I have used bagusflyer's workaround to submit app, but finally I found out how to solve it permanently.

Here is the solution:

1. Accept new changed terms and condition from apple developer account . (Just like Sandeep said)

2. Go to here to generate new provision profiles, for App Store & AdHoc ( Tutorial )

3. Double click new provision profiles you downloaded to install them, and then XCode will never crash.

The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)

After that, you can submit app and export Ad Hoc distribution for Testflight.

Answer 7

I tried all of the other suggestions, no success.

Finally I removed my AppleID from the accounts preferences pane and re-added it. That did the trick!

Since then, app submission was working again.

Answer 8

For me, The problem seems to happen because of uploading same build to the submission. Try to change the Build Number (not a Version number) then upload again.

Answer 9

我设法通过在会员中心接受新的许可协议来解决这个问题。

Answer 10

我在归档时打开了多个项目，关闭了所有其他项目。

Answer 11

4 hours wasted last night with unknown error, didn't even get an error until opened Xcode > Organiser, closed Xcode, then uploaded. Still no joy, moved to Application loader and then hit further errors. Finally upload worked when given the Agent account details, no joy with my Admin account details.

Answer 12

These steps works with Xcode 7.x:

• close Xcode
• launch Disk Utility, make a First Aid to your OSX disk
• open Xcode, go to Window - Project and clean your project Derived Data
• open Window - Organizer
• open Xcode - Preferences - Account and remove and re-add your account
• launch your project
• go to both project and target - Build settings - Build Options (settings) and set "Enable Bitcode" to NO ( if your project don't use bitcode)
• select a real device and build and run your project to the device
• go to product and launch archive