react-native: com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:79)

Same thing here. We are seeing crashes reported in the Play Store crashes & ANR console. This is all we get as the stack trace (I realize it might not be the same network error originally reported in this issue):

Title: com.facebook.react.modules.core.ExceptionsManagerModule.reportException Type: com.facebook.react.common.JavascriptException

Exception com.facebook.react.common.JavascriptException:
  at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:72)
  at java.lang.reflect.Method.invoke
  at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
  at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188)
  at com.facebook.react.bridge.queue.NativeRunnable.run
  at android.os.Handler.handleCallback (Handler.java:751)
  at android.os.Handler.dispatchMessage (Handler.java:95)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
  at android.os.Looper.loop (Looper.java:154)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226)
  at java.lang.Thread.run (Thread.java:762)

happening in Android 7, 10, 11 and 12

In my latest release, this crash is causing too frequently.

The following exception was only seen on Android 13 with SDK 33

Exception com.facebook.react.common.c:
 at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:72)
 at java.lang.reflect.Method.invoke (Method.java)
 at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
 at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188)
 at com.facebook.react.bridge.queue.NativeRunnable.run (NativeRunnable.java)
 at android.os.Handler.handleCallback (Handler.java:942)
 at android.os.Handler.dispatchMessage (Handler.java:99)
 at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
 at android.os.Looper.loopOnce (Looper.java:210)
 at android.os.Looper.loop (Looper.java:299)
 at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226)
 at java.lang.Thread.run (Thread.java:1012)

Hello everyone, I notice that this problem is occurring and being reported by several users (I also have it).

Given the difficulty of reproduction, @dmytrorykun, wouldn’t it be a case to move some people to investigate the hypothesis that it really is related to a React glitch?

@Brunocolaco come on, check this!

I have the same issue but in getting deeper in the logs I found the actual error, which is unrelated to react native. If you have this I would recommend a better crash reporting lib or on the device to use adb get the logs and get the error.

My experience with this issue is that it’s either an uninitialized variable or function.

Firebase Test Lab can be helpful as it can randomly test different modules and screens with input that may be infrequent. Also, virtual devices seem to work better than real hardware, I think because they run slower and more erratically, so they can catch infrequent function calls, etc.

Also, Test Lab gives a better stack trace than Play Store. It will tell you what Class or Module the crash came from.

In my case, I wasn’t testing for non-initialization in componetWillUnmount. This is the corrected version. I think what was happening was that the elements were destroyed prior to the function being called.

componentWillUnmount() {
    this.unsubscribe();
    this.subscribe();
    if (Dimensions.removeEventListener && this.checkOrientation)
      Dimensions.removeEventListener("change", this.checkOrientation);
  }

The other thing is that I think, but am not sure, that you sometimes may be able to reproduce these bugs by changing the code while debugging, and see if it crashes. I used to think that the crashes were just artifacts of the debugging system, but I did notice that it was always crashing inside the above function. Moral of that story is that if you get crashes when updating code while debugging, it’s worth seeing if it’s a problem with your code.

I am also facing this issue - and just like you it happens in a way I can’t reproduce, however, this is a log am seeing in my diagnostics.

Same thing here. We are seeing crashes reported in the Play Store crashes & ANR console. This is all we get as the stack trace (I realize it might not be the same network error originally reported in this issue): Title: com.facebook.react.modules.core.ExceptionsManagerModule.reportException Type: com.facebook.react.common.JavascriptException

Exception com.facebook.react.common.JavascriptException:
  at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:72)
  at java.lang.reflect.Method.invoke
  at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
  at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188)
  at com.facebook.react.bridge.queue.NativeRunnable.run
  at android.os.Handler.handleCallback (Handler.java:751)
  at android.os.Handler.dispatchMessage (Handler.java:95)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
  at android.os.Looper.loop (Looper.java:154)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226)
  at java.lang.Thread.run (Thread.java:762)

happening in Android 7, 10, 11 and 12

conseguiu resolver?

As per my reply (#33916 (comment)) I think you’ll need to integrate some kind of Bug capture tool into your app. From my own research, I don’t think you’ll find any useful answers without integrating a meaningful bug/crash capture tool. I found Bugsnag very easy to implement but there are other out there - just google “react native bug crash capture”. Once I got a meaningful crash message, fixing my problems causing this error was very simple.

I completely agree with you. The description of failures and errors on the Google Play console is very truncated, here in general only the error call stack is described. I use Bugfender and with its help I found what the problem was (in my case it’s one of the libs I use).

just if it will help and give more context, will drop a picture from Google Console: it looks most affected ones are Samsung devices

Same issue, happened on Android 11 (SDK 30)

Exception com.facebook.react.common.JavascriptException:
  at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:72)
  at java.lang.reflect.Method.invoke
  at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
  at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188)
  at com.facebook.react.bridge.queue.NativeRunnable.run
  at android.os.Handler.handleCallback (Handler.java:938)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
  at android.os.Looper.loop (Looper.java:246)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228)
  at java.lang.Thread.run (Thread.java:923)

Version:

• react: 17.0.2
• react-native: 0.68.2

Same problem for me, too (affected Android 10 and Android 12):

Exception com.facebook.react.common.JavascriptException:
  at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:83)
  at java.lang.reflect.Method.invoke
  at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
  at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:151)
  at com.facebook.react.bridge.queue.NativeRunnable.run
  at android.os.Handler.handleCallback (Handler.java:883)
  at android.os.Handler.dispatchMessage (Handler.java:100)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
  at android.os.Looper.loop (Looper.java:214)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226)
  at java.lang.Thread.run (Thread.java:919)

Kajanan02 - try adding in a bug catcher like Sentry (sentry.io) or Bugsnag (bugsnag.com) into your code to catch the details of the crash. That should tell you what’s going wrong

same here, 69% samsung :

`Fatal Exception: com.facebook.react.common.JavascriptException: TypeError: undefined is not a function, js engine: hermes, stack: onError@1798:1356 anonymous@794:5564 anonymous@795:565 anonymous@795:551 _e@30:93552 Ee@30:12998 anonymous@795:530 tryCallOne@53:15 anonymous@139:26 anonymous@78:1691 p@78:527 N@78:917 callReactNativeMicrotasks@78:3078 value@56:2934 anonymous@56:1044 value@56:2582 value@56:1003 value@56:938

   at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
   at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
   at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
   at android.os.Handler.handleCallback(Handler.java:938)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
   at android.os.Looper.loop(Looper.java:246)
   at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
   at java.lang.Thread.run(Thread.java:923)`

@herbertvuijk, Most likely you’ve tried to use a variable without initializing it. Play store doesn’t provide a very good stack trace for this type of thing. Firebase test lab is better. The default random test script works pretty well, and it gives you more detail about where the crash occurred.

Uninitialized variables are also pretty easy to find by just looking through your code or else writing something that can analyze your code to find them. I’ve been meaning to write one, but not yet.

Same issue here. Interesting to see that people are reporting this for more than a year and yet nothing happens.

My experience with this issue is that it’s either an uninitialized variable or function.

This agrees with what I’ve been seeing. For me these errors have been occurring when I try to use a Javascript method on an unititalised variable - e.g join() or trim()

We are impacted by the same issue as well, but not for all users. Affected device in the wild

I think it has to do with react-native-date-picker but I’m not able to reproduce it.

I am just thinking out loud - try resolving all non-fatals, it should disappear.

Someone was writing about disabling progourd, just found out that I was missing -keep class com.swmansion.reanimated.** { *; }(just found in reanimated docs, at first when I was doing it maybe they didn’t have it as I think I would add that line in proguard) from android proguard-rules.pro file, will monitor this change, and will update if it was a problem.

I solved the issue. In my case Platform component needed to be imported from react-native lib. I struggled for days and accidentally found the solution, so maybe look for components that weren’t imported since some phones don’t have them by default (S22 and S21 in my case 😅)

I’m having the same problem. And I can’t reproduce.

Not the best answer out here, but in my case I increased the target SDK and maximum SDK to 33 (latest).