- SDK Version: 4.5.2
- Platforms(Android/iOS/web/all): iOS
- Add the appropriate “Tag” based on what Expo library you have a question on.
expo buid:ios --release-channel test
will generate the ipa that crash imediately on ios .
expo buid:ios --release-channel test
will generate the ipa that crash imediately on ios .
hi Charile . Well I think the problems is that when I build with the --release-channel , app will crash . you can see that if you got the crash from react native . you will got the white page ( js crash ) . but my app crash on open . mean some how it crash from the native code . I can attach the crash log .
Incident Identifier: 5D080E68-91B4-48E2-9DBF-45222B290043
Hardware Model: iPhone10,1
Process: ComGigacoverPocket [838]
Path: /private/var/containers/Bundle/Application/70CE4444-DB34-4208-977F-500EFDD664A6/ExpoKitApp.app/ComGigacoverPocket
Identifier: com.gigacover.pocket
Version: 4 (0.1.5)
AppStoreTools: 12E262
AppVariant: 1:iPhone10,1:14
Beta: YES
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: com.gigacover.pocket [585]
Date/Time: 2021-06-13 20:28:30.6798 +0700
Launch Time: 2021-06-13 20:28:29.3646 +0700
OS Version: iPhone OS 14.5.1 (18E212)
Release Type: User
Baseband Version: 6.51.01
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Last Exception Backtrace:
0 CoreFoundation 0x186f4b128 __exceptionPreprocess + 216 (NSException.m:199)
1 libobjc.A.dylib 0x19ac5e480 objc_exception_throw + 56 (objc-exception.mm:565)
2 ComGigacoverPocket 0x100a30dc8 0x100808000 + 2264520
3 ComGigacoverPocket 0x100a522d8 0x100808000 + 2400984
4 libdispatch.dylib 0x186b83298 0x186b22000 + 397976
5 libdispatch.dylib 0x186b66050 0x186b22000 + 278608
6 libdispatch.dylib 0x186b83298 0x186b22000 + 397976
7 libdispatch.dylib 0x186b65438 0x186b22000 + 275512
8 CoreFoundation 0x186eca170 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1790)
9 CoreFoundation 0x186ec45d0 __CFRunLoopRun + 2528 (CFRunLoop.c:3118)
10 CoreFoundation 0x186ec36a8 CFRunLoopRunSpecific + 572 (CFRunLoop.c:3242)
11 GraphicsServices 0x19d573570 GSEventRunModal + 160 (GSEvent.c:2259)
12 UIKitCore 0x1897e1370 -[UIApplication _run] + 1052 (UIApplication.m:3269)
13 UIKitCore 0x1897e68ec UIApplicationMain + 164 (UIApplication.m:4740)
14 ComGigacoverPocket 0x10080f9f8 0x100808000 + 31224
15 libdyld.dylib 0x186ba2140 0x186ba1000 + 4416
Thread 0 name:
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001b2be07b0 __pthread_kill + 8
1 libsystem_pthread.dylib 0x00000001cf24c9c4 pthread_kill + 212 (pthread.c:1392)
2 libsystem_c.dylib 0x000000018fb3fac0 __abort + 112 (abort.c:147)
3 libsystem_c.dylib 0x000000018fb3fa50 abort + 112 (abort.c:118)
4 libc++abi.dylib 0x000000019ad38be8 abort_message + 128 (abort_message.cpp:78)
5 libc++abi.dylib 0x000000019ad2ad14 demangling_terminate_handler() + 296 (cxa_default_handlers.cpp:67)
6 libobjc.A.dylib 0x000000019ac3e9a0 _objc_terminate() + 124 (objc-exception.mm:701)
7 libc++abi.dylib 0x000000019ad38074 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59)
8 libc++abi.dylib 0x000000019ad3800c std::terminate() + 44 (cxa_handlers.cpp:88)
9 libdispatch.dylib 0x0000000186b832ac 0x186b22000 + 397996
10 libdispatch.dylib 0x0000000186b66050 0x186b22000 + 278608
11 libdispatch.dylib 0x0000000186b83298 0x186b22000 + 397976
12 libdispatch.dylib 0x0000000186b65438 0x186b22000 + 275512
13 CoreFoundation 0x0000000186eca170 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1790)
14 CoreFoundation 0x0000000186ec45d0 __CFRunLoopRun + 2528 (CFRunLoop.c:3118)
15 CoreFoundation 0x0000000186ec36a8 CFRunLoopRunSpecific + 572 (CFRunLoop.c:3242)
16 GraphicsServices 0x000000019d573570 GSEventRunModal + 160 (GSEvent.c:2259)
17 UIKitCore 0x00000001897e1370 -[UIApplication _run] + 1052 (UIApplication.m:3269)
18 UIKitCore 0x00000001897e68ec UIApplicationMain + 164 (UIApplication.m:4740)
19 ComGigacoverPocket 0x000000010080f9f8 0x100808000 + 31224
20 libdyld.dylib 0x0000000186ba2140 0x186ba1000 + 4416
As you can see no information there .
Not necessarily- fatal JS errors can crash your standalone app. If your app doesn’t crash when you expo build:ios --release-channel default
, then there is something in the JavaScript bundle of your test
release channel that is causing the crash. The native code between the two is identical
Hi Charlie . You’re totally right . The code can be crash by fatal JS without lead to white page . And my code to handle the releaseChannel is wrong . Thank for your help
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.