为啥我的 FinderSync 扩展在启动之前就崩溃了？
Posted
技术标签:
【中文标题】为啥我的 FinderSync 扩展在启动之前就崩溃了？【英文标题】：Why is my FinderSync extension crashing before it starts?为什么我的 FinderSync 扩展在启动之前就崩溃了？ 【发布时间】：2019-05-31 06:32:46 【问题描述】：每次我的 FinderSync 扩展启动时都会崩溃：
Process: My Finder Sync [8364]
Path: /Applications/Company/Container.app/Contents/PlugIns/My Finder Sync.appex/Contents/MacOS/My Finder Sync
Identifier: com.company.Container.My-Finder-Sync
Version: [Set on build machine] ([Set on build machine])
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: My Finder Sync [8364]
User ID: 1129915948
Date/Time: 2019-01-04 11:31:34.146 -0500
OS Version: Mac OS X 10.13.6 (17G4015)
Report Version: 12
Anonymous UUID: 013E2942-CED9-22FA-438A-E3D0BA89EB5C
Sleep/Wake UUID: D21EDE9D-237A-412A-8456-B96453886BAD
Time Awake Since Boot: 3200 seconds
Time Since Wake: 2600 seconds
System Integrity Protection: disabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSDictionaryM setObject:forKey:]: object cannot be nil (key: 37990439-1DFE-4F0B-9865-6FC1D34A3BE4)'
terminating with uncaught exception of type NSException
abort() called
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff31eb523b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff59147c76 objc_exception_throw + 48
2 CoreFoundation 0x00007fff31ef64c4 _CFThrowFormattedException + 202
3 CoreFoundation 0x00007fff31db87cc -[__NSDictionaryM setObject:forKey:] + 1020
4 Foundation 0x00007fff3408b348 -[_NSExtensionContextVendor _setPrincipalObject:forUUID:] + 106
5 Foundation 0x00007fff3408ab04 __105-[_NSExtensionContextVendor _beginRequestWithExtensionItems:listenerEndpoint:withContextUUID:completion:]_block_invoke + 804
6 libdispatch.dylib 0x00007fff59d2f5fa _dispatch_call_block_and_release + 12
7 libdispatch.dylib 0x00007fff59d27db8 _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff59d33395 _dispatch_main_queue_callback_4CF + 1148
9 CoreFoundation 0x00007fff31e6db39 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
10 CoreFoundation 0x00007fff31e2fcda __CFRunLoopRun + 2586
11 CoreFoundation 0x00007fff31e2f033 CFRunLoopRunSpecific + 483
12 HIToolbox 0x00007fff31119d96 RunCurrentEventLoopInMode + 286
13 HIToolbox 0x00007fff31119b06 ReceiveNextEventCommon + 613
14 HIToolbox 0x00007fff31119884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
15 AppKit 0x00007fff2f3c9a73 _DPSNextEvent + 2085
16 AppKit 0x00007fff2fb5fe34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
17 AppKit 0x00007fff2f3be885 -[NSApplication run] + 764
18 AppKit 0x00007fff2f38da72 NSApplicationMain + 804
19 libxpc.dylib 0x00007fff5a0bbd77 _xpc_objc_main + 580
20 libxpc.dylib 0x00007fff5a0ba9ca xpc_main + 433
21 Foundation 0x00007fff33f825f5 +[NSXPCListener serviceListener] + 0
22 PlugInKit 0x00007fff50ddbf8d -[PKService run] + 704
23 PlugInKit 0x00007fff50ddbb99 +[PKService main] + 55
24 PlugInKit 0x00007fff50ddbfb1 +[PKService _defaultRun:arguments:] + 17
25 Foundation 0x00007fff34130229 NSExtensionMain + 51
26 libdyld.dylib 0x00007fff59d61015 start + 1
27 ??? 0x0000000000000001 0x0 + 1
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff59eb1b66 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff5a07c080 pthread_kill + 333
2 libsystem_c.dylib 0x00007fff59e0d1ae abort + 127
3 libc++abi.dylib 0x00007fff57d07f8f abort_message + 245
4 libc++abi.dylib 0x00007fff57d0812b default_terminate_handler() + 265
5 libobjc.A.dylib 0x00007fff59149ea3 _objc_terminate() + 97
6 libc++abi.dylib 0x00007fff57d237c9 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fff57d23843 std::terminate() + 51
8 libdispatch.dylib 0x00007fff59d27dcc _dispatch_client_callout + 28
9 libdispatch.dylib 0x00007fff59d33395 _dispatch_main_queue_callback_4CF + 1148
10 com.apple.CoreFoundation 0x00007fff31e6db39 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
11 com.apple.CoreFoundation 0x00007fff31e2fcda __CFRunLoopRun + 2586
12 com.apple.CoreFoundation 0x00007fff31e2f033 CFRunLoopRunSpecific + 483
13 com.apple.HIToolbox 0x00007fff31119d96 RunCurrentEventLoopInMode + 286
14 com.apple.HIToolbox 0x00007fff31119b06 ReceiveNextEventCommon + 613
15 com.apple.HIToolbox 0x00007fff31119884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
16 com.apple.AppKit 0x00007fff2f3c9a73 _DPSNextEvent + 2085
17 com.apple.AppKit 0x00007fff2fb5fe34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
18 com.apple.AppKit 0x00007fff2f3be885 -[NSApplication run] + 764
19 com.apple.AppKit 0x00007fff2f38da72 NSApplicationMain + 804
20 libxpc.dylib 0x00007fff5a0bbd77 _xpc_objc_main + 580
21 libxpc.dylib 0x00007fff5a0ba9ca xpc_main + 433
22 com.apple.Foundation 0x00007fff33f825f5 -[NSXPCListener resume] + 165
23 com.apple.pluginkit.framework 0x00007fff50ddbf8d -[PKService run] + 704
24 com.apple.pluginkit.framework 0x00007fff50ddbb99 +[PKService main] + 55
25 com.apple.pluginkit.framework 0x00007fff50ddbfb1 +[PKService _defaultRun:arguments:] + 17
26 com.apple.Foundation 0x00007fff34130229 NSExtensionMain + 51
27 libdyld.dylib 0x00007fff59d61015 start + 1
Thread 1:
0 libsystem_kernel.dylib 0x00007fff59eb228a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff5a079009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff5a078be9 start_wqthread + 13
Thread 2:
0 libsystem_kernel.dylib 0x00007fff59eb228a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff5a079009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff5a078be9 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff59eb228a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff5a079009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff5a078be9 start_wqthread + 13
Thread 4:
0 libsystem_pthread.dylib 0x00007fff5a078bdc start_wqthread + 0
1 ??? 0x0004000200000006 0 + 1125908496777222
Thread 5:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff59ea820a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff59ea7724 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff31e30665 __CFRunLoopServiceMachPort + 341
3 com.apple.CoreFoundation 0x00007fff31e2f9b7 __CFRunLoopRun + 1783
4 com.apple.CoreFoundation 0x00007fff31e2f033 CFRunLoopRunSpecific + 483
5 com.apple.AppKit 0x00007fff2f506fc4 _NSEventThread + 184
6 libsystem_pthread.dylib 0x00007fff5a079661 _pthread_body + 340
7 libsystem_pthread.dylib 0x00007fff5a07950d _pthread_start + 377
8 libsystem_pthread.dylib 0x00007fff5a078bf9 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff927a7380 rcx: 0x00007ffee31a6c68 rdx: 0x0000000000000000
rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007ffee31a6ca0 rsp: 0x00007ffee31a6c68
r8: 0x00007ffee31a6b30 r9: 0x00007ffee31a6d00 r10: 0x0000000000000000 r11: 0x0000000000000206
r12: 0x0000000000000307 r13: 0x0000000000000030 r14: 0x0000000000000006 r15: 0x000000000000002d
rip: 0x00007fff59eb1b66 rfl: 0x0000000000000206 cr2: 0x00007fff92784168
如您所见，那里只有 Apple 平台的东西。更糟糕的是，这发生在我的任何代码被调用之前！至少，它永远不会在我的FIFinderSync 类'init 中达到我的断点。
那么这里发生了什么？为什么它会因某些字典中的 UUID 键和 nil 值而崩溃？我已经检查了所有代码并确保不会发生这种情况（我确实有一些这样的字典，但所有字典都在 Swift 代码中，并且这些值不是可选的，所以永远不能是 nil；不要介意它们的断点不是' t 击中任何一个）。
【问题讨论】：
【参考方案1】：Swift 会进行一些名称修饰，即使它看起来不像。当您执行诸如通过字符串引用类名之类的操作时，例如在 FinderSync 扩展的 info.plist 中，这在 Swift 中并不总是按预期工作。
例如，如果您有这样的类：
@objc
class MyFinderSyncPrinicpalClass: FIFinderSync
// ...
尝试编译它并查看生成的 Obj-C 标头。它可能看起来像这样：
SWIFT_CLASS("_TtC17My_Finder_Sync10MyFinderSyncPrinicpalClass")
@interface MyFinderSyncPrinicpalClass : FIFinderSync
// ...
@end
这意味着 Swift 和 Objective-C 代码都可以简单地将其称为 MyFinderSyncPrinicpalClass，但是任何想要通过字符串引用其编译形式的东西，例如在反射中或 info.plist，都会看到它被破坏名称_TtC17My_Finder_Sync10MyFinderSyncPrinicpalClass。要解决此问题，只需在 @objc 注释中明确指定名称：
@objc(MyFinderSyncPrinicpalClass)
class MyFinderSyncPrinicpalClass: FIFinderSync
// ...
现在如果你compare that to the newly-generated Obj-C header，你就会明白我的意思了：
SWIFT_CLASS("MyFinderSyncPrinicpalClass")
@interface MyFinderSyncPrinicpalClass : FIFinderSync
// ...
@end
现在您可以在info.plist 中使用它的实际名称来引用它，它会按预期启动！
【讨论】：
在我的情况下没有帮助。我在 ios 感谢您分享您的经验！如果您将其作为另一个答案提交，我一定会投赞成票?【参考方案2】：我的猜测是您的扩展程序的 Info.plist 中的某些内容是错误的。也许那里有一个缺失值，当操作系统试图获取它的值时，它会返回零。然后，当异常发生时，它可能会尝试将该值放入另一个字典中。从涉及的函数名称来看，可能是您的 Principal Class 或 Info.plist 文件中的类似条目丢失。
【讨论】：
感谢您让我走上正确的道路！事实证明，因为我使用 Swift 类作为主要类，所以发生了一些名称修改。即使它是@objc class MyFinderSync: FIFinderSync，我也不得不将其更改为@objc(FinderSync) class MyFinderSync: FIFinderSync，现在它可以工作了！烦人，但很高兴这是一个简单的解决方法。 我应该将其发布在单独的答案中还是您想将其编辑到您的答案中？
听起来你更了解细节。随意发布一个单独的答案。以上是关于为啥我的 FinderSync 扩展在启动之前就崩溃了？的主要内容，如果未能解决你的问题，请参考以下文章
FinderSync 扩展运行时错误：无法打开该文件，因为您无权查看它
Finder Sync 扩展：无法通过 UNIX 域套接字进行通信