5
Android - 2.8.31 - Crash when opening a push notification and app not running
in progress
M
Mobile App
Hello there,
I'm seeing a crash on app startup after opening a push notification. It only seems to happen when the app is not running at all. A notification arrives, I tap on it, the app starts, and the crash happens - right after the splash screen comes up.
When the app is already running in the background, things look fine - I get a Notification Opened event.
Things also work when the app is already running in the foreground - I get a Notification Received event.
I'm seeing this on my ancient Android 6 phone, but also in the Android emulator with a pretty current Android API version 29.
The app is #187603. The build I used for the below stack trace is 169500.
Logcat shows the following stack trace:
07-11 19:10:15.462 4278 4320 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Process: de.denkklima.dev, PID: 4278
07-11 19:10:15.462 4278 4320 E AndroidRuntime: com.facebook.react.common.JavascriptException: TypeError: Cannot read property 'insets' of null
07-11 19:10:15.462 4278 4320 E AndroidRuntime:
07-11 19:10:15.462 4278 4320 E AndroidRuntime: This error is located at:
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in O
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in A
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in ForwardRef
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in ForwardRef
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in P
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in PanGestureHandler
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in P
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in G
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in R
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in h
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in w
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in j
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in ForwardRef
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in ForwardRef
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RNCSafeAreaProvider
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in A
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in c
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in L
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Unknown
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in k
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in Root
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in RCTView
07-11 19:10:15.462 4278 4320 E AndroidRuntime: in x, js engine: v8, stack:
07-11 19:10:15.462 4278 4320 E AndroidRuntime: e.setSafeAreaInsets@1205:2710
07-11 19:10:15.462 4278 4320 E AndroidRuntime: O.value@2483:3131
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Fl@92:76189
07-11 19:10:15.462 4278 4320 E AndroidRuntime: e.unstable_runWithPriority@172:3914
07-11 19:10:15.462 4278 4320 E AndroidRuntime: an@92:24606
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Dl@92:73996
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Pl@92:65221
07-11 19:10:15.462 4278 4320 E AndroidRuntime: <unknown>@92:24877
07-11 19:10:15.462 4278 4320 E AndroidRuntime: e.unstable_runWithPriority@172:3914
07-11 19:10:15.462 4278 4320 E AndroidRuntime: an@92:24606
07-11 19:10:15.462 4278 4320 E AndroidRuntime: sn@92:24823
07-11 19:10:15.462 4278 4320 E AndroidRuntime: cn@92:24758
07-11 19:10:15.462 4278 4320 E AndroidRuntime: _e@92:88067
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Ne@92:13580
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Ue@92:13753
07-11 19:10:15.462 4278 4320 E AndroidRuntime: Object.receiveEvent@92:14162
07-11 19:10:15.462 4278 4320 E AndroidRuntime:
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:71)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:371)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:150)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225)
07-11 19:10:15.462 4278 4320 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
Log In
Activity
Newest
Oldest
Kristian Gerkman
in progress
Kristian Gerkman
Thanks Mobile App ! I'll try to figure out what is the issue here. Like I said in the forum post, I couldn't reproduce this with _just_ push notifications. So I'm assuming it's 1. some logic that is run when the app opens (global canvas? Initial page?) 2. Some component on some the initial page that is opened. 3. something related to push notifications, that is somehow differently configured than in my app.
I have few questions:
- does the app crash when you just open it?
- does the app crash if you receive push notification while the app is open?
- Could you add Notification receivedandNotification openedevents to your global canvas, and see if that helps
Thanks! :)
M
Mobile App
Kristian Gerkman: Thank you very much, Kristian, for looking into this.
To address your questions:
- The app doesn't crash, when I just open it.
- The app doesn't crash, when the app is open and a push notification comes in.
- I am already handling the Notification received and Notification opened events on the global canvas.
Regarding 3) - is there a way for me to log messages from inside the production build of my app that would show up in Android's logcat? The Debug log component only seems to work with the AppGyver debugger, i.e., only from inside the AppGyver preview app.
I'd be happy to write custom JavaScript, if that's what it takes. I would then reproduce the issue and could tell you exactly which events fire leading up to the crash.
Kristian Gerkman
Mobile App: Oh, sorry, I though I talked with you on the forums side.. but this is just same issue. - Thanks for these, I think the only way to see actual logs in a standalone is with our dev tool. I'll try comparing things from this and the app from forums, to see what are the similarities -> I'll try to reproduce this. Could be something not even related to push notifications :)
M
Mobile App
Kristian Gerkman: Thanks again for looking into this! Please do let me know, if you'd like me to provide more information and/or try out more things. Happy to help.
Kristian Gerkman
Mobile App: Hey, I found the cause of the issue, having
WebView
view component installed / on the canvas makes the app crash if you open the app from a notification - I don't have any workaround for this just now, and I'll continue investigations next week to see if it's simple component update, or if it requires new runtime version. Thanks!M
Mobile App
Kristian Gerkman: Awesome! That's great news. Thank you for the effort you put into troubleshooting this issue. Have a good weekend!
M
Mobile App
Kristian Gerkman: FWIW - I managed to do some logging by writing to a file on SD card. It looks like the crash happens before the App Launched, Notification Opened, and Notification Received events fire on my global canvas.
M
Mobile App
Kristian Gerkman: Just noticed that there's a beta release of 2.10.1. Has this issue been addressed in this release? If so, just let me know and I'll be happy to do some more testing.
M
Mobile App
Kristian Gerkman: Hey there. I'm afraid that it looks like the problem still persists in 2.10:
08-16 21:33:05.763 12044 12095 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Process: de.denkklima.dev, PID: 12044
08-16 21:33:05.763 12044 12095 E AndroidRuntime: com.facebook.react.common.JavascriptException: TypeError: Cannot read property 'insets' of null
08-16 21:33:05.763 12044 12095 E AndroidRuntime:
08-16 21:33:05.763 12044 12095 E AndroidRuntime: This error is located at:
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in b
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in A
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in ForwardRef
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in ForwardRef
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in P
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in PanGestureHandler
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in P
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in G
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in R
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in h
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in w
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in j
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in ForwardRef
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in ForwardRef
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RNCSafeAreaProvider
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in A
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in c
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in L
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Unknown
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in k
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in Root
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in RCTView
08-16 21:33:05.763 12044 12095 E AndroidRuntime: in x, js engine: v8, stack:
08-16 21:33:05.763 12044 12095 E AndroidRuntime: e.setSafeAreaInsets@1672:2721
08-16 21:33:05.763 12044 12095 E AndroidRuntime: b.value@2983:3142
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Fl@92:76189
08-16 21:33:05.763 12044 12095 E AndroidRuntime: e.unstable_runWithPriority@172:3914
08-16 21:33:05.763 12044 12095 E AndroidRuntime: an@92:24606
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Dl@92:73996
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Pl@92:65221
08-16 21:33:05.763 12044 12095 E AndroidRuntime: <unknown>@92:24877
08-16 21:33:05.763 12044 12095 E AndroidRuntime: e.unstable_runWithPriority@172:3914
08-16 21:33:05.763 12044 12095 E AndroidRuntime: an@92:24606
08-16 21:33:05.763 12044 12095 E AndroidRuntime: sn@92:24823
08-16 21:33:05.763 12044 12095 E AndroidRuntime: cn@92:24758
08-16 21:33:05.763 12044 12095 E AndroidRuntime: _e@92:88067
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Ne@92:13580
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Ue@92:13753
08-16 21:33:05.763 12044 12095 E AndroidRuntime: Object.receiveEvent@92:14162
08-16 21:33:05.763 12044 12095 E AndroidRuntime:
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:71)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:371)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:150)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225)
08-16 21:33:05.763 12044 12095 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
M
Mobile App
Kristian Gerkman: Just a quick update from my end. This is still an issue with 2.12.2.
I spent some time exploring the issue a little more. To recap, I'm testing the following three different cases:
- App in foreground when the push notification arrives.
- App in background, but still running. (I.e., app in foreground, then push Android's circle button.)
- App not running. (I.e., app in foreground, then push Android's square button, then swipe the app out of the list of apps.)
1 and 2 work fine. The issue is 3. Here's what happens in this case:
i. The incoming push message makes Android send a broadcast, which matches the following receiver in the app's manifest:
io.invertase.firebase.messaging.ReactNativeFirebaseMessagingReceiver
ii. The broadcast message starts the app process. Looking at Invertase's source code for the receiver, in this case (i.e., a newly started app process) the receiver starts a service:
io.invertase.firebase.messaging.ReactNativeFirebaseMessagingHeadlessService
iii. As far as I understand, the service simply invokes a headless JavaScript task:
ReactNativeFirebaseMessagingHeadlessTask
iv. The headless JavaScript task invokes a function provided by AppGyver via the setBackgroundMessageHandler function.
v. Running AppGyver's function seems to leave the app process in a state that causes the crash. When I now either a) click on the push notification or b) simply start the app normally from the Android start screen, the crash happens. So, it doesn't matter how I start the app. Either way, the app seems to be in a state that will make it crash.
As an experiment, I tried killing the app process after step iv. This prevents the crash in both cases, a) when clicking on the push notification and b) when starting the app normally from the Android start screen. This makes sense to me, as killing the app process will a subsequent app start create a new, fresh process that's not in this weird, crash-inducing state.
What also works as a workaround for me is removing the ReactNativeFirebaseMessagingHeadlessService from the APK's manifest. My guess is that this prevents AppGyver's background message handler from running and, thus, prevents the app from getting into a state that would make it crash.
The workaround makes the app come up normally without crashing. However, it obviously doesn't get any notification events, as the background message handler never runs. But for me that's better than crashing.
M
Mobile App
Oh, wow. When I replace the headless JavaScript task ReactNativeFirebaseMessagingHeadlessTask with a do-nothing stub that simply does "return () => Promise.resolve()", then the crash still happens.
So, getting the app process into a crash-inducing state probably isn't related to any function registered with setBackgroundMessageHandler. (Maybe you guys don't even use setBackgroundMessageHandler.)
It seems that just firing up the JavaScript environment to run the headless task messes up the internal state of the app process. Regardless of whether the headless task's JavaScript does anything or not.
Fascinating.
M
Mobile App
Instrumenting the methods of HeadlessJsTaskService (the super class of ReactNativeFirebaseMessagingHeadlessService) yields that the service's lifecycle is as expected. The methods are invoked in the following order:
HeadlessJsTaskService() - constructor
onStartCommand()
startTask()
invokeStartTask()
onHeadlessJsTaskFinish()
onDestroy()
So, onStartCommand() is the first thing the service sees and onDestroy() is the last thing, just as expected.
It's also OK that after onDestroy() the app process remains around. (Proved by running "ps -A" in the shell via adb.) Android does that, just in case another intent needs handling.
What's not OK is that, apparently, even though we go through onDestroy() - which you'd think would reset everything - the service leaves the app process in a state that subsequently causes it to crash.
M
Mobile App
I just tried a build with 2.8.33, which seems to fix things on my Android 6 device. However, when running the app in the Android API 29 emulator, then the issue persists. Stack trace from the emulator for the 2.8.33 build:
07-12 17:12:30.803 5490 5531 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Process: de.denkklima.dev, PID: 5490
07-12 17:12:30.803 5490 5531 E AndroidRuntime: com.facebook.react.common.JavascriptException: TypeError: Cannot read property 'insets' of null
07-12 17:12:30.803 5490 5531 E AndroidRuntime:
07-12 17:12:30.803 5490 5531 E AndroidRuntime: This error is located at:
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in O
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in A
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in ForwardRef
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in ForwardRef
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in P
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in PanGestureHandler
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in P
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in G
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in R
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in h
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in w
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in j
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in ForwardRef
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in ForwardRef
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RNCSafeAreaProvider
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in A
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in c
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in L
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Unknown
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in k
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in Root
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in RCTView
07-12 17:12:30.803 5490 5531 E AndroidRuntime: in x, js engine: v8, stack:
07-12 17:12:30.803 5490 5531 E AndroidRuntime: e.setSafeAreaInsets@1228:2710
07-12 17:12:30.803 5490 5531 E AndroidRuntime: O.value@2559:3131
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Fl@92:76189
07-12 17:12:30.803 5490 5531 E AndroidRuntime: e.unstable_runWithPriority@172:3914
07-12 17:12:30.803 5490 5531 E AndroidRuntime: an@92:24606
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Dl@92:73996
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Pl@92:65221
07-12 17:12:30.803 5490 5531 E AndroidRuntime: <unknown>@92:24877
07-12 17:12:30.803 5490 5531 E AndroidRuntime: e.unstable_runWithPriority@172:3914
07-12 17:12:30.803 5490 5531 E AndroidRuntime: an@92:24606
07-12 17:12:30.803 5490 5531 E AndroidRuntime: sn@92:24823
07-12 17:12:30.803 5490 5531 E AndroidRuntime: cn@92:24758
07-12 17:12:30.803 5490 5531 E AndroidRuntime: _e@92:88067
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Ne@92:13580
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Ue@92:13753
07-12 17:12:30.803 5490 5531 E AndroidRuntime: Object.receiveEvent@92:14162
07-12 17:12:30.803 5490 5531 E AndroidRuntime:
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:71)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:371)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:150)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225)
07-12 17:12:30.803 5490 5531 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
M
Mobile App
Ah, sorry, I have to take back a part of my previous comment: I just saw the crash with 2.8.33 also on my Android 6 phone.
Also, I did a 2.8.33 iOS build today - and so far it doesn't seem to have this issue. So, currently this seems to be specific to Android.