致命异常：iOS上的NSInternalInconsistencyException崩溃

几天来，我一直在试图重新创造和研究这个问题，我哪儿也不去。这是堆栈跟踪。有人能解释发生了什么事吗？我认为这与远程通知有关。这个问题早在我安装firebase sdk时就开始了。当时事故并不多，但现在，车祸似乎比平常更频繁

致命异常：NSInternalInconsistencyException 此请求已被阉割-您不能调用-sendResponse:两次，也不能在编码后调用 +[[u CFXNotificationTokenRegistration keyCallbacks]

Fatal Exception: NSInternalInconsistencyException
0  CoreFoundation                 0x1c2726ab8 __exceptionPreprocess
1  libobjc.A.dylib                0x1c192bd00 objc_exception_throw
2  CoreFoundation                 0x1c263be90 +[_CFXNotificationTokenRegistration keyCallbacks]
3  Foundation                     0x1c3117cfc -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]
4  BaseBoard                      0x1c4f2e664 __40-[BSAction sendResponse:withCompletion:]_block_invoke
5  libdispatch.dylib              0x1c2135888 _dispatch_client_callout
6  libdispatch.dylib              0x1c2142404 _dispatch_lane_barrier_sync_invoke_and_complete
7  BaseBoard                      0x1c4ee2b84 -[BSAction sendResponse:withCompletion:]
8  UIKitCore                      0x1ef72bf84 -[UIHandleRemoteNotificationAction sendResponse:]
9  UIKitCore                      0x1efb69028 __91-[UIApplication _handleNonLaunchSpecificActions:forScene:withTransitionContext:completion:]_block_invoke_3.2678
10 UIKitCore                      0x1efb69b4c __125-[UIApplication _updateStateRestorationArchiveForBackgroundEvent:saveState:exitIfCouldNotRestoreState:updateSnapshot:canvas:]_block_invoke_2
11 libdispatch.dylib              0x1c2134308 _dispatch_call_block_and_release
12 libdispatch.dylib              0x1c2135888 _dispatch_client_callout
13 libdispatch.dylib              0x1c214173c _dispatch_main_queue_callback_4CF
14 CoreFoundation                 0x1c26b6734 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
15 CoreFoundation                 0x1c26b13e4 __CFRunLoopRun
16 CoreFoundation                 0x1c26b0964 CFRunLoopRunSpecific
17 GraphicsServices               0x1c48f1d8c GSEventRunModal
18 UIKitCore                      0x1efb51758 UIApplicationMain
19 XXXX                       0x1023e1480 main + 26 (AppDelegate.swift:26)
20 libdyld.dylib                  0x1c216cfd8 start

Crashed: com.twitter.crashlytics.ios.exception
0  XXXX                       0x102692000 CLSProcessRecordAllThreads + 4305018880
1  XXXX                       0x1026923e8 CLSProcessRecordAllThreads + 4305019880
2  XXXX                       0x102681c60 CLSHandler + 4304952416
3  XXXX                       0x102690604 __CLSExceptionRecord_block_invoke + 4305012228
4  libdispatch.dylib              0x1c2135888 _dispatch_client_callout + 20
5  libdispatch.dylib              0x1c2142404 _dispatch_lane_barrier_sync_invoke_and_complete + 60
6  XXXX                       0x102690070 CLSExceptionRecord + 4305010800
7  XXXX                       0x10268fe9c CLSExceptionRecordNSException + 4305010332
8  XXXX                       0x10268fa90 CLSTerminateHandler() + 4305009296
9  libc++abi.dylib                0x1c19209cc std::__terminate(void (*)()) + 20
10 libc++abi.dylib                0x1c1920a40 std::terminate() + 60
11 libobjc.A.dylib                0x1c192c09c _destroyAltHandlerList + 14
12 libdispatch.dylib              0x1c213589c _dispatch_client_callout + 40
13 libdispatch.dylib              0x1c2142404 _dispatch_lane_barrier_sync_invoke_and_complete + 60
14 BaseBoard                      0x1c4ee2b84 -[BSAction sendResponse:withCompletion:] + 148
15 UIKitCore                      0x1ef72bf84 -[UIHandleRemoteNotificationAction sendResponse:] + 148
16 UIKitCore                      0x1efb69028 __91-[UIApplication _handleNonLaunchSpecificActions:forScene:withTransitionContext:completion:]_block_invoke_3.2678 + 76
17 UIKitCore                      0x1efb69b4c __125-[UIApplication _updateStateRestorationArchiveForBackgroundEvent:saveState:exitIfCouldNotRestoreState:updateSnapshot:canvas:]_block_invoke_2 + 264
18 libdispatch.dylib              0x1c2134308 _dispatch_call_block_and_release + 32
19 libdispatch.dylib              0x1c2135888 _dispatch_client_callout + 20
20 libdispatch.dylib              0x1c214173c _dispatch_main_queue_callback_4CF + 1012
21 CoreFoundation                 0x1c26b6734 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
22 CoreFoundation                 0x1c26b13e4 __CFRunLoopRun + 1888
23 CoreFoundation                 0x1c26b0964 CFRunLoopRunSpecific + 452
24 GraphicsServices               0x1c48f1d8c GSEventRunModal + 108
25 UIKitCore                      0x1efb51758 UIApplicationMain + 216
26 XXXX                       0x1023e1480 main + 26 (AppDelegate.swift:26)
27 libdyld.dylib                  0x1c216cfd8 start + 4

---

为问题添加跟踪是一件好事，但一些进一步的故障排除会有所帮助。它似乎在发送响应时崩溃了-可能是在关闭时。您是否添加了一些打印语句以尝试隔离崩溃的代码部分？你知道它是哪一部分吗？如果是，你能把它包括在问题中吗？您是否正在使用Firebase进行任何通知？请花点时间回顾一下Crashlytics前端中的哪个框架受到了指责？如果对这些stacktraces中出现的Crashlytics框架有任何混淆，请参阅本文档：“……这意味着在出现异常的情况下，“崩溃”线程看起来总是在运行Crashlytics代码。这是正常的，只是我们在异常时如何捕获和显示堆栈跟踪的产物。”