TestFlight 安装的应用程序因 Swift 包管理器依赖项而崩溃 [英] TestFlight installed app crash with Swift Package Manager dependencies
问题描述
我们已经迁移了一些 CocoaPod 依赖项，以便在 Xcode 11 中构建并与 Swift Package Manager 链接.但是，每当我们将应用程序提交到 AppStore Connect 并使用 TestFlight 分发时，应用程序在它尝试从一个应用程序使用 API 的那一刻崩溃SPM 链接的依赖项.其他构建(即席和开发)运行良好.一些 SPM 依赖项还链接了 2 个应用扩展.
We have migrated some of our CocoaPod dependencies to be build and linked with Swift Package Manager in Xcode 11. However, whenever we submit application to AppStore Connect and distribute with TestFlight, the app crashes the moment it tries to use API from one of the SPM linked dependencies. Other builds (adhoc and development) are working fine. Some of the SPM dependencies are also linked 2 app extensions.
有没有人遇到过这个问题，你知道是什么问题和/或如何解决吗?
Did anyone encounter this issue, would you have any idea what is the problem and/or how to fix it?
附加崩溃的堆栈跟踪.这个发生在 ObjectMapper 依赖项中.
Attaching stack trace for the crash. This one happens in ObjectMapper dependency.
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x00000000800000d0
Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [19562]
Triggered by Thread: 0
Thread 0 name:
Thread 0 Crashed:
0 OurAwesomeApp 0x0000000101693d14 nominal type descriptor for EnumTransform + 0
1 OurAwesomeApp 0x000000010108cda0 <- infix<A>(_:_:) + 612 (__hidden#1488_:38)
2 OurAwesomeApp 0x0000000101074434 <- infix<A>(_:_:) + 100 (__hidden#434_:36)
3 OurAwesomeApp 0x0000000100cad360 TWSplitParticipant.mapping(map:) + 1388 (DataClasses.swift:1211)
4 OurAwesomeApp 0x00000001010842cc Mapper.map(JSON:) + 1224 (__hidden#1191_:106)
5 OurAwesomeApp 0x0000000101087c70 _hidden#1144_ + 24 (__hidden#110_:0)
6 libswiftCore.dylib 0x000000018f3cd61c $sSTsE10compactMapySayqd__Gqd__Sg7ElementQzKXEKlF + 732 (SequenceAlgorithms.swift:807)
7 OurAwesomeApp 0x0000000101084a68 Mapper.mapArray(JSONArray:) + 212 (__hidden#1191_:166)
8 OurAwesomeApp 0x0000000101082a8c Mapper.mapArray(JSONObject:) + 192 (__hidden#1191_:156)
9 OurAwesomeApp 0x00000001010753d4 _hidden#461_ + 148 (__hidden#487_:92)
10 OurAwesomeApp 0x0000000101088c8c _hidden#1301_ + 196
11 OurAwesomeApp 0x0000000100cac720 TWSplitRequest.mapping(map:) + 812 (DataClasses.swift:1157)
12 OurAwesomeApp 0x00000001010842cc Mapper.map(JSON:) + 1224 (__hidden#1191_:106)
13 OurAwesomeApp 0x0000000101082988 Mapper.map(JSONObject:) + 160 (__hidden#1191_:89)
14 OurAwesomeApp 0x00000001010752f0 _hidden#459_ + 644 (__hidden#487_:66)
15 OurAwesomeApp 0x000000010108896c <- infix<A>(_:_:) + 152 (__hidden#1307_:116)
16 OurAwesomeApp 0x0000000100ca7248 TWInvoice.mapping(map:) + 4000 (DataClasses.swift:377)
17 OurAwesomeApp 0x00000001010842cc Mapper.map(JSON:) + 1224 (__hidden#1191_:106)
18 OurAwesomeApp 0x0000000101087c70 _hidden#1144_ + 24 (__hidden#110_:0)
19 libswiftCore.dylib 0x000000018f3cd61c $sSTsE10compactMapySayqd__Gqd__Sg7ElementQzKXEKlF + 732 (SequenceAlgorithms.swift:807)
20 OurAwesomeApp 0x0000000101084a68 Mapper.mapArray(JSONArray:) + 212 (__hidden#1191_:166)
21 OurAwesomeApp 0x0000000101082a8c Mapper.mapArray(JSONObject:) + 192 (__hidden#1191_:156)
22 OurAwesomeApp 0x00000001010753d4 _hidden#461_ + 148 (__hidden#487_:92)
23 OurAwesomeApp 0x0000000101088c8c _hidden#1301_ + 196
24 OurAwesomeApp 0x0000000100ca5b88 TWInvoicesByType.mapping(map:) + 328 (DataClasses.swift:266)
25 OurAwesomeApp 0x00000001010842cc Mapper.map(JSON:) + 1224 (__hidden#1191_:106)
26 OurAwesomeApp 0x0000000101082988 Mapper.map(JSONObject:) + 160 (__hidden#1191_:89)
27 OurAwesomeApp 0x00000001010752f0 _hidden#459_ + 644 (__hidden#487_:66)
28 OurAwesomeApp 0x000000010108896c <- infix<A>(_:_:) + 152 (__hidden#1307_:116)
29 OurAwesomeApp 0x0000000100ca3adc TWAccount.mapping(map:) + 104 (DataClasses.swift:81)
30 OurAwesomeApp 0x00000001010842cc Mapper.map(JSON:) + 1224 (__hidden#1191_:106)
31 OurAwesomeApp 0x0000000101082988 Mapper.map(JSONObject:) + 160 (__hidden#1191_:89)
32 OurAwesomeApp 0x0000000100c47c18 closure #1 in DataServer.getAccountInfo(_:) + 492 (DataServer.swift:949)
33 OurAwesomeApp 0x00000001011d7888 _hidden#2846_ + 164
34 OurAwesomeApp 0x00000001011db76c _hidden#2893_ + 52 (__hidden#578_:0)
35 OurAwesomeApp 0x00000001011b55e0 _hidden#996_ + 28 (__hidden#578_:0)
36 libdispatch.dylib 0x0000000181e29610 _dispatch_call_block_and_release + 24 (init.c:1408)
37 libdispatch.dylib 0x0000000181e2a184 _dispatch_client_callout + 16 (object.m:495)
38 libdispatch.dylib 0x0000000181e0d35c _dispatch_main_queue_callback_4CF$VARIANT$armv81 + 996 (inline_internal.h:2487)
39 CoreFoundation 0x00000001820da3c4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1749)
40 CoreFoundation 0x00000001820d53b8 __CFRunLoopRun + 2004 (CFRunLoop.c:3069)
41 CoreFoundation 0x00000001820d48bc CFRunLoopRunSpecific + 464 (CFRunLoop.c:3192)
42 GraphicsServices 0x000000018bf40328 GSEventRunModal + 104 (GSEvent.c:2246)
43 UIKitCore 0x000000018616a6d4 UIApplicationMain + 1936 (UIApplication.m:4753)
44 OurAwesomeApp 0x0000000100c1048c main + 68 (OurAwesomeFactoryFactory.swift:25)
45 libdyld.dylib 0x0000000181f5f460 start + 4
推荐答案
2019-11-27 更新
在 相关的 Swift 错误帖子，有人找到了解决方法:
In the related Swift bug post, somebody has found a workaround:
在我们应用的目标中设置 DEAD_CODE_STRIPPING = NO 修复了崩溃.
Setting DEAD_CODE_STRIPPING = NO in our app’s target fixes the crash.
<小时>
原帖
首先，是SPM的编译问题.只需回滚到 CocoaPods.
First of all, it is a compiling issue of SPM. Simply just rollback to CocoaPods.
直到 Xcode 11.2.1，Apple 还没有修复这个问题.
Until Xcode 11.2.1, Apple has not yet fixed this issue.
删除所有派生文件，清理工程.然后尝试使用 release 配置运行您的项目.现在您应该能够重现崩溃.
Delete all the derived files, clean the project. And then try running your project with the release configuration. Now you should be able to reproduce the crash.
我在 iOS 项目中使用了两个名为 Moya 和 Parchment 的库，其中包含从 CocoaPods 迁移的 Swift 包管理器.执行引用两个库的逻辑时，从 TestFlight 下载的应用程序崩溃.
I was using two libs named Moya and Parchment in an iOS project, with Swift Package Manager, migrated from CocoaPods. And the app downloaded from TestFlight crashes when the logic referencing the two libs is executed.
而且崩溃日志看起来完全是胡说八道，指向一个方法的方法描述符的内存对齐问题.
And the crash log looks completely like nonsense, pointing to a memory alignment issue of the method descriptor of a method.
Apple 在 Xcode 发行说明中提到了一个已知问题，不知道是否相关:
Apple mentioned a known issue in Xcode release note, I don't know if it is related:
如果 iOS、tvOS 或 watchOS 应用使用构建动态库的 Swift Package，则无法提交到 App Store.(55564324)
If an iOS, tvOS, or watchOS app uses a Swift Package that builds a dynamic library, it cannot be submitted to the App Store. (55564324)
解决方法:修改包清单以构建静态库.
Workaround: Modify the Package manifest to build a static library.
这篇关于TestFlight 安装的应用程序因 Swift 包管理器依赖项而崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
