Best IT Recipes

Xcode 6 crashes while checking or sending application archive

This worked great 2 days ago using the same archive and training profile (selected from the organizer). Has anyone else seen this? I have not updated Xcode, so it seems like it could be something on Apple causing the crash?

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)
+60
ios xcode
Sep 16 '14 at 0:33
source share
12 answers

Make sure you accept all new agreements at the Member Center.

To check if you need it, you can go to settings → accounts in Xcode and choose to view account information and try to update using a small button. This is where Xcode warns you that you need to accept new agreements in the Member Center before you can upgrade.

On the other hand, the Organizer will simply collapse, and will not warn you about unsigned agreements.

+62
Sep 24 '14 at 22:13
source share

I solved the problem:

  • Export ipa in organizer
  • Using Application Loader to load ipa storage into an application
+30
Sep 16 '14 at 3:21
source share

I found a solution / workaround at https://devforums.apple.com/ . Message from 優 Yu:

"Open the Organizer by running Arches. Close only the xcode body. Do not close the Organizer screen. Please go and send a Test in this state. I am glad if we can help you."

Works for me, but after checking, I got a strange message:

"The resulting API analysis file is too large. We were unable to verify your use of the API before delivery. This is just an informational message."

I ignored it and successfully sent the app to the App Store. It looks like Apple broke the verification system because I submitted the application 5 days ago without any problems.

+29
Sep 16 '14 at 16:36
source share

Yes, it looks like Apple just removed the option to boot from Xcode 6. Or use Xcode 5.1.1 or Applauncher 2.9.1

+2
Sep 16 '14 at 16:55
source share

Simply accept the new License and Agreement at the developer.apple.com Member Center.

+1
Sep 26 '14 at 6:38
source share

I used the bagusflyer workaround to submit the application, but finally I found out how to solve it forever.

Here is the solution:

  • Accept the new amended terms and conditions from the Apple Developer Report . (Just as Sandeep said)

  • Go here to generate new submission profiles for the App Store and AdHoc ( tutorial )

  • Double-click the new provisioning profiles that you downloaded to install them, and then Xcode never crashes.

The problem arises because Xcode 6.0 does not handle profile profile migration properly. Developers should regenerate the provisioning profiles for Xcode 6+, but Xcode 6.0 will not be able to correctly display this error message and will work. (If you use the beta version of Xcode 6.1, it will display error messages for you, without crashing. Then you will find out that the problem is caused by an "invalid" == "outdated" provisioning profile.)

After that, you can send the application and export the Ad Hoc for Testflight.

+1
Sep 26 '14 at 7:03
source share

I tried all the other suggestions, no success.

Finally, I removed my AppleID from the account settings panel and added it again. It did the trick!

Since then, the application has been working again.

+1
Nov 14 '14 at 8:36
source share

For me, the problem seems to be due to the fact that it is loading into the assembly. Try changing the build number (not the version number) and then download again.

0
Sep 16 '14 at 14:52
source share

I was able to solve this problem by accepting a new license agreement at the Member Center.

0
Sep 26 '14 at 5:37
source share

I had several projects open during archiving, closing all the others.

0
Feb 13 '15 at 11:19
source share

4 hours wasted last night with an unknown error, did not even receive an error message until Xcode> Organizer, closed by Xcode, opens, and then boots up. Still no joy, switched to the application loader and then hit further errors. Finally, the download was performed when providing information about the agent account, without the joy of the information about my administrator account.

0
Jun 19 '15 at 13:59 on
source share

These steps work with Xcode 7.x:

  • close Xcode
  • run Disk Utility, do first aid on your OSX drive.
  • open Xcode, go to Window - Project and clean your project. Derived data
  • open window - organizer
  • open Xcode - Settings - Account and delete and re-add your account
  • run the project
  • go to the project and the target - set the parameters - set the parameters (settings) and set "Enable bitcode" to NO (if your project does not use the bitcode)
  • select the real device and create and run the project on the device
  • go to the product and run the archive
0
Sep 13 '16 at 7:29
source share


More articles:


All Articles