的XCode 6.3崩溃时存档应用

我刚才已经更新到最新的的XCode 6.3和雨燕1.2的XCode 6.3崩溃时存档应用

现在，当我试图存档我们的分销目的之前工作的应用中，我们看到消息“存档成功”，但XCODE崩溃之后立即（组织者通常会打开）。

任何人有什么想法？

下面是从崩溃日志的详细信息...

Process:    Xcode [88096] 
Path:     /Applications/Xcode.app/Contents/MacOS/Xcode 
Identifier:   com.apple.dt.Xcode 
Version:    6.3 (7569) 
Build Info:   IDEFrameworks-7569000000000000~2 
App Item ID:   497799835 
App External ID:  812135760 
Code Type:    X86-64 (Native) 
Parent Process:  ??? [1] 
Responsible:   Xcode [88096] 
User ID:    501 

Date/Time:    2015-04-12 10:52:10.085 -0700 
OS Version:   Mac OS X 10.10.3 (14D131) 
Report Version:  11 
Anonymous UUID:  5EF93B73-2BD1-E454-9891-7EB1F8CC17B5 


Time Awake Since Boot: 230000 seconds 

Crashed Thread:  13 Dispatch queue: NSOperationQueue 0x7f9f87725a70 :: NSOperation 0x7f9f8792a1f0 (QOS: USER_INITIATED) 

Exception Type:  EXC_CRASH (SIGABRT) 
Exception Codes:  0x0000000000000000, 0x0000000000000000 

Application Specific Information: 
ProductBuildVersion: 6D570 
UNCAUGHT EXCEPTION (NSInvalidArgumentException): *** -[NSURL URLByAppendingPathComponent:]: component, components, or pathExtension cannot be nil. 
UserInfo: (null) 
Hints: None 
Backtrace: 
    0 0x00007fff8901b024 __exceptionPreprocess (in CoreFoundation) 
    1 0x000000010765d184 DVTFailureHintExceptionPreprocessor (in DVTFoundation) 
    2 0x00007fff88aa876e objc_exception_throw (in libobjc.A.dylib) 
    3 0x00007fff8901aeed +[NSException raise:format:] (in CoreFoundation) 
    4 0x00007fff90f7781d -[NSURL(NSURLPathUtilities) URLByAppendingPathComponent:] (in Foundation) 
    5 0x000000010a395a41 -[DVTSourceControlWorkspaceBlueprint saveBlueprintInFolder:options:] (in DVTSourceControl) 
    6 0x00000001082e6b61 __96+[IDEArchive _copySCMBlueprintFromWorkspace:toArchiveWithPath:usingFileManager:completionBlock:]_block_invoke (in IDEFoundation) 
    7 0x000000010a38cc24 __77-[DVTSourceControlWorkspace blueprintWithRemoteRepositories:completionBlock:]_block_invoke (in DVTSourceControl) 
    8 0x00007fff90fb77e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ (in Foundation) 
    9 0x00007fff90fb75b5 -[NSBlockOperation main] (in Foundation) 
10 0x00007fff90fb6a6c -[__NSOperationInternal _start:] (in Foundation) 
11 0x00007fff90fb6543 __NSOQSchedule_f (in Foundation) 
12 0x00007fff8841ec13 _dispatch_client_callout (in libdispatch.dylib) 
13 0x00007fff88422365 _dispatch_queue_drain (in libdispatch.dylib) 
14 0x00007fff88423ecc _dispatch_queue_invoke (in libdispatch.dylib) 
15 0x00007fff884216b7 _dispatch_root_queue_drain (in libdispatch.dylib) 
16 0x00007fff8842ffe4 _dispatch_worker_thread3 (in libdispatch.dylib) 
17 0x00007fff89254637 _pthread_wqthread (in libsystem_pthread.dylib) 
18 0x00007fff8925240d start_wqthread (in libsystem_pthread.dylib) 

abort() called 

Application Specific Signatures: 
NSInvalidArgumentException 

Application Specific Backtrace 1: 
0 CoreFoundation      0x00007fff8901b03c __exceptionPreprocess + 172 
1 DVTFoundation      0x000000010765d184 DVTFailureHintExceptionPreprocessor + 194 
2 libobjc.A.dylib      0x00007fff88aa876e objc_exception_throw + 43 
3 CoreFoundation      0x00007fff8901aeed +[NSException raise:format:] + 205 
4 Foundation       0x00007fff90f7781d -[NSURL(NSURLPathUtilities) URLByAppendingPathComponent:] + 84 
5 DVTSourceControl     0x000000010a395a41 -[DVTSourceControlWorkspaceBlueprint saveBlueprintInFolder:options:] + 225 
6 IDEFoundation      0x00000001082e6b61 __96+[IDEArchive _copySCMBlueprintFromWorkspace:toArchiveWithPath:usingFileManager:completionBlock:]_block_invoke + 112 
7 DVTSourceControl     0x000000010a38cc24 __77-[DVTSourceControlWorkspace blueprintWithRemoteRepositories:completionBlock:]_block_invoke + 5293 
8 Foundation       0x00007fff90fb77e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 
9 Foundation       0x00007fff90fb75b5 -[NSBlockOperation main] + 97 
10 Foundation       0x00007fff90fb6a6c -[__NSOperationInternal _start:] + 653 
11 Foundation       0x00007fff90fb6543 __NSOQSchedule_f + 184 
12 libdispatch.dylib     0x00007fff8841ec13 _dispatch_client_callout + 8 
13 libdispatch.dylib     0x00007fff88422365 _dispatch_queue_drain + 1100 
14 libdispatch.dylib     0x00007fff88423ecc _dispatch_queue_invoke + 202 
15 libdispatch.dylib     0x00007fff884216b7 _dispatch_root_queue_drain + 463 
16 libdispatch.dylib     0x00007fff8842ffe4 _dispatch_worker_thread3 + 91 
17 libsystem_pthread.dylib    0x00007fff89254637 _pthread_wqthread + 729 
18 libsystem_pthread.dylib    0x00007fff8925240d start_wqthread + 13

来源

2015-04-12 YamYam

是的，它肯定是在Xcode的问题。我们可以使用命令行工具来构建应用程序。

我发现一个解决方案虽然工作;

我打消了我的个人设置从.xcodeproj xcuserdata并在project.xcworkspace

重新加载到XCODE删除这些设置后固定的问题。

来源

2015-04-12 20:11:37 YamYam

这不适合我，但感谢分享 – donmarkusi

看起来像这样的问题是，当你有一个老的项目与一些子项目在源代码控制下，而主要的不是。

我已经完全从Xcode首选项源代码控制中删除，它似乎做了伎俩 - 现在归档工程。

要从源代码管理中删除项目，请按命令+，（或从主菜单中选择首选项） - >源代码管理，然后取消选中所有参数。

我在开发人员论坛中关注此问题，并且似乎Apple知道这些问题。

新项目不受影响。

从Xcode 6.3: Crash while archiving a project

来源

2015-04-15 18:14:32

我有同样的问题。从源代码控制中删除所有东西解决了它。感谢Shefali – befstrat

做到了这一招，thx！ – chritaso

回答这是在XCode中6.3的错误。如果你想保持这个源代码控制下，升级到6.3.1的XCode

从发行说明：

归档包含源代码控制内容的项目或工作，是不是源代码管理下，但呢不会崩溃Xcode。（20521089）

来源

2015-04-22 08:39:09

的XCode 6.3崩溃时存档应用

回答

相关问题