"TestFlight React Native Expo 在啟動時崩潰"

Question

我很失望，因為我在使用 Expo 管理的 react native 應用程序。 到這里為止，一切正常。 我的 TestFlight 版本運行良好，但今天我遇到了一個新問題。 我在 TestFlight 上的所有構建在啟動時都會崩潰。 一開始，我在想我的一個錯誤，但是當我嘗試重新安裝我的舊版本時（我確信它們可以工作，因為我測試了它）應用程序面臨同樣的錯誤。 所以，我的理論是，我的 TestFlight 版本將獲取一個 Apple 服務器，而他可能無法......所以它崩潰了......你有什么想法還是你認為 Apple 是問題所在？

有我的崩潰日志，我驗證了它在我的舊版本上的崩潰與我上次版本的崩潰相同。

Thread 0 name:
Thread 0 Crashed:
0   libsystem_kernel.dylib          0x00000001b8003334 __pthread_kill + 8
1   libsystem_pthread.dylib         0x00000001d5a89a9c pthread_kill + 272 (pthread.c:1582)
2   libsystem_c.dylib               0x00000001930c5c10 __abort + 128 (abort.c:155)
3   libsystem_c.dylib               0x00000001930c5b90 abort + 136 (abort.c:126)
4   libc++abi.dylib                 0x000000019e8e9bb8 abort_message + 132 (abort_message.cpp:78)
5   libc++abi.dylib                 0x000000019e8daec8 demangling_terminate_handler() + 308 (cxa_default_handlers.cpp:67)
6   libobjc.A.dylib                 0x000000019e7e705c _objc_terminate() + 144 (objc-exception.mm:701)
7   libc++abi.dylib                 0x000000019e8e8fa0 std::__terminate(void (*)()) + 20 (cxa_handlers.cpp:59)
8   libc++abi.dylib                 0x000000019e8e8f2c std::terminate() + 48 (cxa_handlers.cpp:88)
9   libdispatch.dylib               0x00000001898eb830 _dispatch_client_callout + 40 (object.m:562)
10  libdispatch.dylib               0x00000001898fa9ec _dispatch_async_and_wait_invoke + 96 (queue.c:1545)
11  libdispatch.dylib               0x00000001898eb81c _dispatch_client_callout + 20 (object.m:559)
12  libdispatch.dylib               0x00000001898f9c70 _dispatch_main_queue_callback_4CF + 884 (inline_internal.h:2557)
13  CoreFoundation                  0x0000000189c78340 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 (CFRunLoop.c:1790)
14  CoreFoundation                  0x0000000189c72218 __CFRunLoopRun + 2524 (CFRunLoop.c:3118)
15  CoreFoundation                  0x0000000189c71308 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3242)
16  GraphicsServices                0x00000001a12f4734 GSEventRunModal + 164 (GSEvent.c:2259)
17  UIKitCore                       0x000000018c6ef75c -[UIApplication _run] + 1072 (UIApplication.m:3269)
18  UIKitCore                       0x000000018c6f4fcc UIApplicationMain + 168 (UIApplication.m:4740)
19  ComMlDevSpiritApp               0x0000000100259e78 main + 88 (main.m:8)
20  libdyld.dylib                   0x000000018992dcf8 start + 4

https://pastebin.com/JbyrRwQQ

Answer 1

我有關於這次崩潰的新信息。 當我打開我的設備日志時，我會在所有構建中得到它......：

Unable to simultaneously satisfy constraints.
    Probably at least one of the constraints in the following list is one you don't want. 
    Try this: 
        (1) look at each constraint and try to figure out which you don't expect; 
        (2) find the code that added the unwanted constraint or constraints and fix it. 
(
    "<NSLayoutConstraint:0x281394af0 V:|-(>=0)-[UIImageView:0x121d05150]   (active, names: '|':UIView:0x11fd156f0 )>",
    "<NSLayoutConstraint:0x281394b90 V:[UIImageView:0x121d05150]-(10)-[UIView:0x11fd156f0]   (active)>"
)

Will attempt to recover by breaking constraint 
<NSLayoutConstraint:0x281394b90 V:[UIImageView:0x121d05150]-(10)-[UIView:0x11fd156f0]   (active)>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
BackgroundSession <B601EDD8-BACA-4FF5-8715-E0ECABBACBF1> connection to background transfer daemon invalidated



Invariant Violation: Native module cannot be null.


Unhandled JS Exception: Invariant Violation: Native module cannot be null.

Answer 2

運行 expo build:android 或 expo build:ios 而不是使用 eas。 您仍然可以使用 eas submit。