앱 아카이브 유효성 검사 또는 제출시 Xcode 6 충돌
이틀 전에는 정확히 동일한 보관 및 프로비저닝 프로필 (주최자에서 선택)을 사용하여 제대로 작동했습니다. 이걸 본 사람이 있나요? Xcode를 업데이트하지 않았으므로 Apple 측에서 오류를 일으키는 것 같습니까?
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)
회원 센터에서 새로운 계약을 모두 수락했는지 확인하십시오.
필요한지 확인하려면 XCode의 기본 설정-> 계정으로 이동하여 계정 세부 정보 를 보고 작은 버튼을 사용하여 새로 고침 을 시도 할 수 있습니다. 여기에서 XCode는 새로 고침하기 전에 회원 센터에서 새로운 계약에 동의해야한다고 경고합니다.
반면에 Organizer는 서명되지 않은 계약에 대해 경고하는 대신 충돌합니다.
나는 다음과 같이 문제를 해결했다.
- Organizer에서 ipa 내보내기
- Using Application Loader to load the ipa to app store
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.
Yes it looks like apple just withdrew the option to upload with XCode 6. Either use XCode 5.1.1 or Applauncher 2.9.1
Simply Accept the new License and Agreement in developer.apple.com 's Member Center.
I have used bagusflyer's workaround to submit app, but finally I found out how to solve it permanently.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
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.
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.
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.
I managed to solve this issue by accepting new license agreement in the Member's Center.
I had multiple projects opened while archiving, closing all others worked.
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.
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
'Programing' 카테고리의 다른 글
| 몇 분 전에 액세스 / 생성 된 파일을 찾는 방법 (0) | 2020.12.04 |
|---|---|
| 가동 중지 시간없이 런타임에 elasticsearch 클러스터에서 노드를 제거하는 방법 (0) | 2020.12.04 |
| R에서 함수 곡선을 그리는 방법 (0) | 2020.12.04 |
| std :: unique_ptr을 함수에 어떻게 전달할 수 있습니까? (0) | 2020.12.04 |
| 함수의 반환 유형 얻기 (0) | 2020.12.04 |