前端之家

  1. 首页
  2. 问答

针对iOS的构建因线程1而失败：在iOS 12.4上发出信号SIGABRT

• 问答

我突然发现iOS 12.4上的错误Thread 1: signal SIGABRT。

一旦应用开始运行并显示启动画面，这就是我所看到的。

针对iOS的构建因线程1而失败：在iOS 12.4上发出信号SIGABRT

这在iOS 12.4上发生，但在iOS 13.2上没有发生。我检查了我的存储库的较早提交，其中该问题不存在，但没有帮助。

回溯：

{\rtf1\ansi\ansicpg1252\cocoartf1671\cocoasubrtf600
{\fonttbl\f0\fnil\fcharset0 Menlo-Regular;\f1\fnil\fcharset0 Menlo-Bold;}
{\colortbl;\red255\green255\blue255;\red255\green255\blue255;\red31\green31\blue36;}
{\*\expandedcolortbl;;\csgenericrgb\c100000\c100000\c100000;\csgenericrgb\c12054\c12284\c14131;}
\paperw11900\paperh16840\margl1440\margr1440\vieww10800\viewh8400\viewkind0
\deftab593
\pard\tx593\pardeftab593\pardirnatural\partightenfactor0

\f0\fs24 \cf2 \cb3 thread #1,queue = 'com.apple.main-thread',stop reason = signal SIGABRT
\f1\b \

\f0\b0     frame #0: 0x00000001190313ae dyld`__abort_with_payload + 10
\f1\b \

\f0\b0     frame #1: 0x0000000119030ba0 dyld`abort_with_payload_wrapper_internal + 82
\f1\b \

\f0\b0     frame #2: 0x0000000119030bd2 dyld`abort_with_payload + 9
\f1\b \

\f0\b0     frame #3: 0x000000010eb8d8c1 dyld_sim`abort_with_payload + 34
\f1\b \

\f0\b0     frame #4: 0x000000010eb84fe0 dyld_sim`dyld::halt(char const*) + 343
\f1\b \

\f0\b0     frame #5: 0x000000010eb8510a dyld_sim`dyld::fastBindLazySymbol(ImageLoader**,unsigned long) + 167
\f1\b \

\f0\b0     frame #6: 0x00000001185a4122 libdyld.dylib`dyld_stub_binder + 282
\f1\b \

\f0\b0     frame #7: 0x000000010eb2e000 Relation Portal
\f1\b \

\f0\b0     frame #8: 0x000000010eb0ae0e Relation Portal`-[CDVViewController __init](self=0x00007f8cfbe07b30,_cmd="__init") at CDVViewController.m:82:9
\f1\b \

\f0\b0     frame #9: 0x000000010eb0aefe Relation Portal`-[CDVViewController initWithNibName:bundle:](self=0x00007f8cfbe07b30,_cmd="initWithNibName:bundle:",nibNameOrNil=0x0000000000000000,nibBundleOrNil=0x0000000000000000) at CDVViewController.m:91:5
\f1\b \

\f0\b0     frame #10: 0x000000010ead2bb4 Relation Portal`-[MainViewController initWithNibName:bundle:](self=0x0000000000000000,nibBundleOrNil=0x0000000000000000) at MainViewController.m:34:12
\f1\b \

\f0\b0     frame #11: 0x000000010eb0b05b Relation Portal`-[CDVViewController init](self=0x0000000000000000,_cmd="init") at CDVViewController.m:104:12
\f1\b \

\f0\b0     frame #12: 0x000000010ead2c6b Relation Portal`-[MainViewController init](self=0x0000000000000000,_cmd="init") at MainViewController.m:46:12
\f1\b \

\f0\b0     frame #13: 0x000000010ead2aa5 Relation Portal`-[AppDelegate application:didFinishlaunchingWithOptions:](self=0x0000600003200d20,_cmd="application:didFinishlaunchingWithOptions:",application=0x00007f8cfe000e50,launchOptions=0x0000000000000000) at AppDelegate.m:35:27
\f1\b \

\f0\b0     frame #14: 0x000000011edab731 UIKitCore`-[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 280
\f1\b \

\f0\b0     frame #15: 0x000000011edad0cd UIKitCore`-[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 3932
\f1\b \

\f0\b0     frame #16: 0x000000011edb24e6 UIKitCore`-[UIApplication _runWithMainScene:transitionContext:completion:] + 1617
\f1\b \

\f0\b0     frame #17: 0x000000011e5f6a4e UIKitCore`__111-[__UICanvasLifecyclemonitor_Compatability _scheduleFirstCommitForScene:transition:firstactivation:completion:]_block_invoke + 904
\f1\b \

\f0\b0     frame #18: 0x000000011e5ff346 UIKitCore`+[_UICanvas _enqueuePostSettingUpdateTransactionBlock:] + 153
\f1\b \

\f0\b0     frame #19: 0x000000011e5f6664 UIKitCore`-[__UICanvasLifecyclemonitor_Compatability _scheduleFirstCommitForScene:transition:firstactivation:completion:] + 236
\f1\b \

\f0\b0     frame #20: 0x000000011e5f6fc0 UIKitCore`-[__UICanvasLifecyclemonitor_Compatability activateEventsonly:withContext:completion:] + 1091
\f1\b \

\f0\b0     frame #21: 0x000000011e5f5332 UIKitCore`__82-[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:]_block_invoke + 782
\f1\b \

\f0\b0     frame #22: 0x000000011e5f4fe9 UIKitCore`-[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:] + 433
\f1\b \

\f0\b0     frame #23: 0x000000011e5f9d2e UIKitCore`__125-[_UICanvasLifecycleSettingsDiffaction performactionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:]_block_invoke + 576
\f1\b \

\f0\b0     frame #24: 0x000000011e5fa988 UIKitCore`_performactionsWithDelayForTransitionContext + 100
\f1\b \

\f0\b0     frame #25: 0x000000011e5f9a95 UIKitCore`-[_UICanvasLifecycleSettingsDiffaction performactionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:] + 223
\f1\b \

\f0\b0     frame #26: 0x000000011e5fea48 UIKitCore`-[_UICanvas scene:didUpdateWithDiff:transitionContext:completion:] + 392
\f1\b \

\f0\b0     frame #27: 0x000000011edb0dc8 UIKitCore`-[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 514
\f1\b \

\f0\b0     frame #28: 0x000000011e96802f UIKitCore`-[UIApplicationSceneclientAgent scene:didInitializeWithEvent:completion:] + 361
\f1\b \

\f0\b0     frame #29: 0x000000011dbdfd25 FrontBoardServices`-[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 448
\f1\b \

\f0\b0     frame #30: 0x000000011dbe9ad6 FrontBoardServices`__56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 283
\f1\b \

\f0\b0     frame #31: 0x000000011dbe9300 FrontBoardServices`__40-[FBSWorkspace _performDelegateCallOut:]_block_invoke + 53
\f1\b \

\f0\b0     frame #32: 0x000000011852ddb5 libdispatch.dylib`_dispatch_client_callout + 8
\f1\b \

\f0\b0     frame #33: 0x00000001185312ba libdispatch.dylib`_dispatch_block_invoke_direct + 300
\f1\b \

\f0\b0     frame #34: 0x000000011dc1b0da FrontBoardServices`__FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 30
\f1\b \

\f0\b0     frame #35: 0x000000011dc1ad92 FrontBoardServices`-[FBSSerialQueue _performNext] + 451
\f1\b \

\f0\b0     frame #36: 0x000000011dc1b327 FrontBoardServices`-[FBSSerialQueue _performNextFromRunLoopSource] + 42
\f1\b \

\f0\b0     frame #37: 0x0000000110cf0db1 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
\f1\b \

\f0\b0     frame #38: 0x0000000110cf0633 CoreFoundation`__CFRunLoopDoSources0 + 243
\f1\b \

\f0\b0     frame #39: 0x0000000110ceacef CoreFoundation`__CFRunLoopRun + 1231
\f1\b \

\f0\b0     frame #40: 0x0000000110cea4d2 CoreFoundation`CFRunLoopRunSpecific + 626
\f1\b \

\f0\b0     frame #41: 0x00000001133ba2fe GraphicsServices`GSEventRunmodal + 65
\f1\b \

\f0\b0     frame #42: 0x000000011edb3fc2 UIKitCore`UIApplicationmain + 140
\f1\b \

\f0\b0   * frame #43: 0x000000010ead2a21 Relation Portal`main(argc=1,argv=0x00007ffee112d238) at main.m:32:22
\f1\b \

\f0\b0     frame #44: 0x00000001185a2541 libdyld.dylib`start + 1
\f1\b \

\f0\b0     frame #45: 0x00000001185a2541 libdyld.dylib`start + 1}
xiaobiw9527 回答：针对iOS的构建因线程1而失败：在iOS 12.4上发出信号SIGABRT

printMultiTaskingInfo中的问题是由我的config.xml引起的。以下值会在旧版iOS上导致错误：

<preference name="orientation" value="portrait" />

别忘了做

ionic build

之后。这就是我为什么仍然遇到错误的主要原因。

,

您可以尝试将打印功能明确地放在主线程中！

enter image description here

enter image description here

它必须与主线程有关。

出于测试目的，不做任何更改，请取消选中主线程检查器，然后尝试运行它以获取清晰的图片，

enter image description here

cordovaionic-frameworkionic-nativeiosxcode
本文链接：https://www.f2er.com/3154024.html

大家都在问