search

facebook / react-native

A framework for building native applications using React
https://reactnative.dev
MIT License
118.24k stars 24.22k forks source link

com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:79) #33916

Closed nmanvitha closed 1 year ago

nmanvitha commented 2 years ago

Description

Hi,

In Android the app randomly crashing with the below error. Got this in firebase crashlytics dashboard and there is no log to debug and reproduce. and We see this crash mostly happens on Samsung devices.

Fatal Exception: com.facebook.react.common.JavascriptException TypeError: null is not an object (evaluating 'U.networkType.value'), stack: onValueChange@1368:4730 onPress@954:1602 onPress@229:1700 value@225:7540 value@225:6753 onResponderRelease@225:5556 b@99:1125 S@99:1268 w@99:1322 R@99:1617 M@99:2401 forEach@-1 U@99:2201 @99:13818 Pe@99:90199 Re@99:13478 Ie@99:13664 receiveTouches@99:14448 value@40:3544 @40:840 value@40:2798 value@40:812 value@-1

Below are the dependencies.

"@burstware/react-native-portal": "^1.0.2", "@react-native-community/async-storage": "^1.9.0", "@react-native-community/datetimepicker": "3.0.0", "@react-native-community/geolocation": "^2.0.2", "@react-native-community/masked-view": "^0.1.7", "@react-native-community/netinfo": "^5.9.5", "@react-native-community/progress-bar-android": "^1.0.3", "@react-native-community/progress-view": "@1.1.1", "@react-native-firebase/analytics": "^7.4.2", "@react-native-firebase/app": "^8.3.1", "@react-native-firebase/crashlytics": "^8.3.3", "@react-navigation/bottom-tabs": "5.2.6", "@react-navigation/drawer": "5.0.5", "@react-navigation/material-bottom-tabs": "5.1.7", "@react-navigation/material-top-tabs": "5.1.7", "@react-navigation/native": "5.1.4", "@react-navigation/native-stack": "5.0.5", "@react-navigation/stack": "5.2.9", "android": "^0.0.8", "axios": "^0.19.2", "format-string-by-pattern": "^1.2.1", "jail-monkey": "^2.3.2", "jsc-android": "^245459.0.0", "moment": "^2.24.0", "patch-package": "^6.4.7", "prop-types": "^15.7.2", "react": "16.11.0", "react-native": "0.62.1", "react-native-add-calendar-event": "3.0.2", "react-native-awesome-card-io": "^0.8.3", "react-native-background-timer": "^2.2.0", "react-native-collapsible": "^1.5.2", "react-native-config": "1.3.3", "react-native-device-info": "^5.6.1", "react-native-document-picker": "^4.1.0", "react-native-easy-toast": "^1.2.0", "react-native-exit-app": "^1.1.0", "react-native-fs": "2.16.6", "react-native-gesture-handler": "1.8.0", "react-native-get-random-values": "^1.4.0", "react-native-htmlview": "^0.15.0", "react-native-image-base64": "0.1.4", "react-native-image-picker": "2.3.1", "react-native-image-resizer": "1.2.3", "react-native-image-zoom-viewer": "3.0.1", "react-native-in-app-review": "^2.1.5", "react-native-languages": "^3.0.2", "react-native-linear-gradient": "^2.5.6", "react-native-localization": "^2.1.6", "react-native-map-clustering": "^3.3.4", "react-native-maps": "^0.27.1", "react-native-modal": "^11.5.6", "react-native-orientation-locker": "^1.0.21", "react-native-pdf": "^6.2.0", "react-native-permissions": "2.1.4", "react-native-picker-select": "^6.6.0", "react-native-rate": "^1.2.1", "react-native-reanimated": "^1.8.0", "react-native-safe-area-context": "^0.7.3", "react-native-screens": "@2.4.0", "react-native-share": "^5.1.0", "react-native-signature-capture": "^0.4.11", "react-native-snap-carousel": "^3.9.0", "react-native-splash-screen": "^3.2.0", "react-native-sqlite-storage": "https://github.com/leorajdsouza/react-native-sqlite-storage.git", "react-native-svg": "^12.1.0", "react-native-tab-view": "2.13.0", "react-native-touch-id": "^4.4.1", "react-native-user-inactivity": "^1.1.0", "react-native-vector-icons": "6.6.0", "react-native-webview": "~9.1.4", "react-redux": "^7.2.0", "reanimated-bottom-sheet": "^1.0.0-alpha.19", "redux": "^4.0.5", "redux-logger": "^3.0.6", "redux-thunk": "^2.3.0", "rn-fetch-blob": "^0.12.0", "rn-secure-storage": "^2.0.4", "underscore": "^1.12.0"

Any solution??

Version

0.62.1

Output of npx react-native info

No response

Steps to reproduce

Got it in Firebase Crashlytics.

Snack, code example, screenshot, or link to a repository

No response

vaish8529 commented 1 year ago

Got similar issue from play console Crashes and ANRs

Description com.facebook.react.common.c Exception com.facebook.react.common.c: at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java) at java.lang.reflect.Method.invoke (Method.java) at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java) at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java) 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) at android.os.Looper.loop (Looper.java:246) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java) at java.lang.Thread.run (Thread.java:923)

Version 0.63.3

Output of npx react-native info info Fetching system and libraries information... System: OS: Windows 10 10.0.22621 CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-12650H Memory: 5.91 GB / 15.68 GB Binaries: Node: 14.20.1 - C:\Program Files\nodejs\node.EXE Yarn: Not Found npm: 6.14.17 - C:\Program Files\nodejs\npm.CMD Watchman: Not Found SDKs: Android SDK: API Levels: 29, 30, 31, 33 Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 33.0.0 System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64, android-30 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-31 | Intel x86 Atom_64, android-31 | Google APIs ARM 64 v8a, android-31 | Google APIs Intel x86 Atom_64, android-33 | Google APIs ARM 64 v8a, android-33 | Google APIs Intel x86 Atom_64, android-33 | Google Play Intel x86 Atom_64 Android NDK: Not Found Windows SDK: Not Found IDEs: Android Studio: AI-213.7172.25.2113.9014738 Visual Studio: Not Found Languages: Java: 11.0.16 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE Python: Not Found npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.63.3 => 0.63.3 react-native-windows: Not Found npmGlobalPackages: react-native: Not Found

Steps to reproduce Crash reports on Play Console

Snack, code example, screenshot, or link to a repository Exception com.facebook.react.common.c: at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java) at java.lang.reflect.Method.invoke (Method.java) at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java) at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java) 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) at android.os.Looper.loop (Looper.java:246) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java) at java.lang.Thread.run (Thread.java:923)

pera14 commented 1 year ago

I have the same issue. Any solution?

corintijohnson commented 1 year ago

I am having the same issue...Any solution?

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.loopOnce (Looper.java:226) at android.os.Looper.loop (Looper.java:313) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228) at java.lang.Thread.run (Thread.java:1012)

beqramo commented 1 year ago

just if it will help and give more context, will drop a picture from Google Console:

image

it looks most affected ones are Samsung devices

pera14 commented 1 year ago

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 😅)

n-kulic commented 1 year ago

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 😅)

So in some file you used Platform without import? If that is so, you can avoid that with eslint which will show errors and warnings in such cases.

I will go through project in detail and see if i missed anything

pera14 commented 1 year ago

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 😅)

So in some file you used Platform without import? If that is so, you can avoid that with eslint which will show errors and warnings in such cases.

I will go through project in detail and see if i missed anything

However, I didn't get that kind of error. I managed to run use the app through Expo on the same phone but I got the issue when I built it and publish to Google Play store. Even then, the error happened only on Samsung S22 and Samsung S21. I tested on 32 different Android phones and didn't get any kind of issue

beqramo commented 1 year ago

for sure I have it imported everywhere, if not eslint would throw an error.

orodrigu commented 1 year ago

Dear, I had the same problem, I started to redo my application, each step was complied and tested in Firebase Test Lab, at the beginning everything was fine until I installed the library npm install @react-navigation/native 6.x and my application It gave me the error that we are all having, in the documentation https://reactnavigation.org/docs/getting-started it indicates that we have to do one more step

Add the following code to the body of MainActivity class:

@Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(null); }

my application uses expo cli and I can't find the MainActivity to make these changes, so I had to go from version 6.x to 5.x of react navigate and the problem was fixed, but a new one came out with the react-native-reanimated package that is installed with react navigate, but very easy to solve

After the installation completes, you must also add the Babel plugin to babel.config.js:

module.exports = function (api) { api.cache(true); return { presets: ['babel-preset-expo'], plugins: ['react-native-reanimated/plugin'], }; };

https://docs.expo.dev/versions/latest/sdk/reanimated/

I hope it works for you.

Cheers

beqramo commented 1 year ago

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.

KolissnikBogdan commented 1 year ago

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.

@beqramo Hi, if I don't use react-native-reanimated in the project, but I use react-navigation and react-native-screens, adding -keep class com.swmansion.reanimated.** { *; } solve this problem? What do you think?

andresribeiro commented 1 year ago

somehow this bug was hapenning on v66 of my app, but it stopped ocurring when I released v67. in this version i just changed some js code and upgraded my dependencies

- "@react-native-firebase/app": "^16.3.0",
- "@react-native-firebase/messaging": "^16.3.0",
+ "@react-native-firebase/app": "^16.4.0",
+ "@react-native-firebase/messaging": "^16.4.0",
- "react-native-pager-view": "^6.0.1",
+ "react-native-pager-view": "^6.0.2",
- "zustand": "^4.1.3"
+ "zustand": "^4.1.4"
- "@babel/runtime": "^7.20.0",
- "@commitlint/cli": "^17.1.2",
- "@commitlint/config-conventional": "^17.1.0",
- "@graphql-codegen/cli": "^2.13.8",
- "@graphql-codegen/typescript": "^2.8.0",
- "@graphql-codegen/typescript-operations": "^2.5.5",
- "@graphql-codegen/typescript-react-apollo": "^3.3.5",
+ "@babel/runtime": "^7.20.1",
+ "@commitlint/cli": "^17.2.0",
+ "@commitlint/config-conventional": "^17.2.0",
+ "@graphql-codegen/cli": "^2.13.11",
+ "@graphql-codegen/typescript": "^2.8.1",
+ "@graphql-codegen/typescript-operations": "^2.5.6",
+ "@graphql-codegen/typescript-react-apollo": "^3.3.6",
- "@types/jest": "^29.2.0",
+ "@types/jest": "^29.2.1",
- "@typescript-eslint/eslint-plugin": "^5.41.0",
- "@typescript-eslint/parser": "^5.41.0",
+ "@typescript-eslint/eslint-plugin": "^5.42.0",
+ "@typescript-eslint/parser": "^5.42.0",
beqramo commented 1 year ago

@KolissnikBogdan no, you don't need, if you are using react navigation 6 it doesn't have dependency on reanimated

https://reactnavigation.org/docs/getting-started/

GerardoIbarra commented 1 year ago

Same issue. Any solution?

image

douglasscriptore commented 1 year ago

Same issue..

KolissnikBogdan commented 1 year ago

+1

lyseiha commented 1 year ago

+1

realabbas commented 1 year ago

Same issue

henriqueadonai commented 1 year ago

Same issue

waslinux commented 1 year ago

Same issue

gconts commented 1 year ago

I am facing same issue with below dependencies

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.jni.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.loopOnce (Looper.java:201)
  at android.os.Looper.loop (Looper.java:288)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228)
  at java.lang.Thread.run (Thread.java:920)

"dependencies": { "@react-native-async-storage/async-storage": "^1.17.11", "@react-native-community/datetimepicker": "6.7.1", "@react-navigation/drawer": "^6.5.6", "@react-navigation/native": "^6.1.1", "@react-navigation/native-stack": "^6.9.7", "eas-cli": "^3.1.1", "expo": "~47.0.9", "expo-image-picker": "^14.0.2", "expo-secure-store": "~12.0.0", "expo-status-bar": "~1.4.2", "expo-updates": "~0.15.6", "react": "18.2.0", "react-native": "0.70.6", "react-native-animatable": "^1.3.3", "react-native-bouncy-checkbox": "^3.0.6", "react-native-date-picker": "^4.2.6", "react-native-gesture-handler": "^2.8.0", "react-native-linear-gradient": "^2.6.2", "react-native-paper": "^5.1.0", "react-native-reanimated": "~2.13.0" }

prasadjayasinghe84 commented 1 year ago

I am facing same issue with below dependencies

"@react-native-async-storage/async-storage": "^1.17.7", "@react-native-community/geolocation": "^3.0.3", "@react-navigation/drawer": "^6.4.3", "@react-navigation/native": "^6.0.10", "@react-navigation/native-stack": "^6.6.2", "axios": "^1.1.3", "react": "18.0.0", "react-native": "0.69.0", "react-native-animatable": "^1.3.3", "react-native-date-picker": "^4.2.2", "react-native-dotenv": "^3.3.1", "react-native-gesture-handler": "^2.5.0", "react-native-linear-gradient": "^2.5.6", "react-native-reanimated": "^2.9.1", "react-native-safe-area-context": "^4.3.1", "react-native-screens": "^3.13.1", "react-native-sqlite-storage": "^6.0.1", "react-native-vector-icons": "^9.2.0"

nazim-musayev commented 1 year ago

I am facing this issue in my all production apps (3 apps). I found this crash details at Google Play Store which indicates startHeadlessTask function. I did not aware of this bug until customer complaints. In last days I had to send new release, so I was debugging and this crash happened also in debug mode (happened when app is in background and I was coming back to the app) and now it iwas clear to me which exact line gives that error . Line 303 in some file.

'node_modules/react-native/Libraries/ReactNative/AppRegistry.js'

This was never happened when I build the app. I tried to compare my AppRegistry.js file with the React-native last version's AppRegistry.js file. And I saw additional 'if check' in line 341. (!(global.RN$Bridgeless === true)).

I would like to know if this is the reason why this issue exists and upgrading app version is going to solve this issue.

Thanks in advance!

stack_trace

crash_report

nazim-musayev commented 1 year ago

debug_error

Dependencies:

"@gorhom/bottom-sheet": "^4.2.1",
"@hookform/resolvers": "^2.8.8",
"@notifee/react-native": "^5.7.0",
"@papercups-io/chat-widget-native": "^1.0.5",
"@react-native-async-storage/async-storage": "^1.17.3",
"@react-native-clipboard/clipboard": "^1.10.0",
"@react-native-community/netinfo": "^9.3.0",
"@react-native-community/push-notification-ios": "^1.10.1",
"@react-native-firebase/analytics": "^15.7.0",
"@react-native-firebase/app": "^15.7.0",
"@react-native-firebase/messaging": "^15.7.0",
"@react-native-picker/picker": "^2.4.1",
"@react-navigation/drawer": "^6.4.1",
"@react-navigation/native": "^6.0.10",
"@react-navigation/stack": "^6.2.1",
"axios": "^0.26.1",
"babel-plugin-module-resolver": "^4.1.0",
"i18n-js": "^3.9.2",
"i18next": "^21.8.9",
"react": "17.0.2",
"react-hook-form": "^7.30.0",
"react-i18next": "^11.17.1",
"react-native": "0.68.1",
"react-native-date-picker": "^4.2.0",
"react-native-device-info": "^10.2.1",
"react-native-dotenv": "^3.3.1",
"react-native-fbsdk-next": "^11.0.0",
"react-native-flip-card": "^3.5.6",
"react-native-gesture-handler": "^2.4.0",
"react-native-image-picker": "^4.10.0",
"react-native-keyboard-aware-scroll-view": "^0.9.5",
"react-native-keychain": "^8.1.1",
"react-native-linear-gradient": "^2.6.2",
"react-native-maps": "^0.31.0",
"react-native-modal": "^13.0.1",
"react-native-picker-select": "^8.0.4",
"react-native-progress": "^5.0.0",
"react-native-reanimated": "^2.7.0",
"react-native-render-html": "^6.3.4",
"react-native-safe-area-context": "^4.2.4",
"react-native-screens": "^3.13.1",
"react-native-splash-screen": "^3.3.0",
"react-native-svg": "^12.3.0",
"react-native-svg-transformer": "^1.0.0",
"react-native-toast-message": "^2.1.5",
"react-native-version-check": "^3.4.3",
"react-native-webview": "^11.23.1",
"react-query": "^3.39.1",
"recoil": "^0.7.2",
"yup": "^0.32.11"
Sun-Woo-Kim commented 1 year ago

Same issue

OskarEichler commented 1 year ago

Same issue

gconts commented 1 year ago

I recently faced this problem. Developed an app using expo. Works fine in development but when I published the app to play store it crashed after the splash screen. Google crashes and ANRs reported Screenshot from 2023-01-02 18-50-34

I download the Signed, universal APK from google play console and installed it in android emulator. and ran adb logcat --buffer=crash

--------- beginning of crash
01-01 23:08:39.849  6040  6091 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
01-01 23:08:39.849  6040  6091 E AndroidRuntime: Process: com.gconts.gym, PID: 6040
01-01 23:08:39.849  6040  6091 E AndroidRuntime: com.facebook.react.common.JavascriptException: Invariant Violation: requireNativeComponent: "RNSScreenStackHeaderConfig" was not found in the UIManager.
01-01 23:08:39.849  6040  6091 E AndroidRuntime: 
01-01 23:08:39.849  6040  6091 E AndroidRuntime: This error is located at:
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RNSScreenStackHeaderConfig
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RNSScreen
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in y
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in f
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Suspense
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in _
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in c
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in c
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in O
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in f
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Suspense
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in _
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RNSScreenStack
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in ScreenStack
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in D
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RNCSafeAreaProvider
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in h
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in o
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RCTView
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RCTView
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in RCTView
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in Unknown
01-01 23:08:39.849  6040  6091 E AndroidRuntime:     in b, stack:
01-01 23:08:39.849  6040  6091 E AndroidRuntime: <unknown>@20:289
01-01 23:08:39.849  6040  6091 E AndroidRuntime: <unknown>@162:1681
01-01 23:08:39.849  6040  6091 E AndroidRuntime: <unknown>@132:919
01-01 23:08:39.849  6040  6091 E AndroidRuntime: ua@34:65870
01-01 23:08:39.849  6040  6091 E AndroidRuntime: Ci@34:86515
01-01 23:08:39.849  6040  6091 E AndroidRuntime: Ri@34:86397
01-01 23:08:39.849  6040  6091 E AndroidRuntime: _i@34:86264
01-01 23:08:39.849  6040  6091 E AndroidRuntime: Ei@34:86029
01-01 23:08:39.849  6040  6091 E AndroidRuntime: yi@34:82985
01-01 23:08:39.849  6040  6091 E AndroidRuntime: yi@-1
01-01 23:08:39.849  6040  6091 E AndroidRuntime: xt@34:27509
01-01 23:08:39.849  6040  6091 E AndroidRuntime: ci@34:79668
01-01 23:08:39.849  6040  6091 E AndroidRuntime: Zi@34:94613
01-01 23:08:39.849  6040  6091 E AndroidRuntime: <unknown>@34:100839
01-01 23:08:39.849  6040  6091 E AndroidRuntime: <unknown>@347:1279
01-01 23:08:39.849  6040  6091 E AndroidRuntime: run@338:1403
01-01 23:08:39.849  6040  6091 E AndroidRuntime: runApplication@338:2420
01-01 23:08:39.849  6040  6091 E AndroidRuntime: value@63:3821
01-01 23:08:39.849  6040  6091 E AndroidRuntime: <unknown>@63:759
01-01 23:08:39.849  6040  6091 E AndroidRuntime: value@63:2583
01-01 23:08:39.849  6040  6091 E AndroidRuntime: value@63:731
01-01 23:08:39.849  6040  6091 E AndroidRuntime: value@-1
01-01 23:08:39.849  6040  6091 E AndroidRuntime: 
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at com.facebook.jni.NativeRunnable.run(Native Method)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:938)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:99)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:223)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
01-01 23:08:39.849  6040  6091 E AndroidRuntime:    at java.lang.Thread.run(Thread.java:923)
01-01 23:09:05.761  6604  6631 E AndroidRuntime: FATAL EXCEPTION: expo-updates-error-recovery
01-01 23:09:05.761  6604  6631 E AndroidRuntime: Process: com.gconts.gym, PID: 6604
01-01 23:09:05.761  6604  6631 E AndroidRuntime: com.facebook.react.common.JavascriptException: Invariant Violation: requireNativeComponent: "RNSScreenStackHeaderConfig" was not found in the UIManager.
01-01 23:09:05.761  6604  6631 E AndroidRuntime: 
01-01 23:09:05.761  6604  6631 E AndroidRuntime: This error is located at:
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RNSScreenStackHeaderConfig
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RNSScreen
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in y
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in f
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Suspense
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in _
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in c
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in c
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in O
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in f
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Suspense
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in _
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RNSScreenStack
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in ScreenStack
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in D
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RNCSafeAreaProvider
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in h
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in o
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RCTView
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RCTView
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in RCTView
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in Unknown
01-01 23:09:05.761  6604  6631 E AndroidRuntime:     in b, stack:
01-01 23:09:05.761  6604  6631 E AndroidRuntime: <unknown>@20:289
01-01 23:09:05.761  6604  6631 E AndroidRuntime: <unknown>@162:1681
01-01 23:09:05.761  6604  6631 E AndroidRuntime: <unknown>@132:919
01-01 23:09:05.761  6604  6631 E AndroidRuntime: ua@34:65870
01-01 23:09:05.761  6604  6631 E AndroidRuntime: Ci@34:86515
01-01 23:09:05.761  6604  6631 E AndroidRuntime: Ri@34:86397
01-01 23:09:05.761  6604  6631 E AndroidRuntime: _i@34:86264
01-01 23:09:05.761  6604  6631 E AndroidRuntime: Ei@34:86029
01-01 23:09:05.761  6604  6631 E AndroidRuntime: yi@34:82985
01-01 23:09:05.761  6604  6631 E AndroidRuntime: yi@-1
01-01 23:09:05.761  6604  6631 E AndroidRuntime: xt@34:27509
01-01 23:09:05.761  6604  6631 E AndroidRuntime: ci@34:79668
01-01 23:09:05.761  6604  6631 E AndroidRuntime: Zi@34:94613
01-01 23:09:05.761  6604  6631 E AndroidRuntime: <unknown>@34:100839
01-01 23:09:05.761  6604  6631 E AndroidRuntime: <unknown>@347:1279
01-01 23:09:05.761  6604  6631 E AndroidRuntime: run@338:1403
01-01 23:09:05.761  6604  6631 E AndroidRuntime: runApplication@338:2420
01-01 23:09:05.761  6604  6631 E AndroidRuntime: value@63:3821
01-01 23:09:05.761  6604  6631 E AndroidRuntime: <unknown>@63:759
01-01 23:09:05.761  6604  6631 E AndroidRuntime: value@63:2583
01-01 23:09:05.761  6604  6631 E AndroidRuntime: value@63:731
01-01 23:09:05.761  6604  6631 E AndroidRuntime: value@-1
01-01 23:09:05.761  6604  6631 E AndroidRuntime: 
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at com.facebook.jni.NativeRunnable.run(Native Method)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:938)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:99)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:223)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
01-01 23:09:05.761  6604  6631 E AndroidRuntime:    at java.lang.Thread.run(Thread.java:923)

The problem in my case was with the versions of packages. Below combination of versions worked for me.

"@react-native-async-storage/async-storage": "^1.17.3",
    "@react-native-community/datetimepicker": "6.5.2",
    "@react-navigation/drawer": "^6.3.1",
    "@react-navigation/native": "^6.0.10",
    "@react-navigation/native-stack": "^6.5.0",
    "expo": "~47.0.0",
    "expo-image-picker": "^14.0.2",
    "expo-secure-store": "~12.0.0",
    "expo-status-bar": "~1.4.2",
    "expo-updates": "~0.15.6",
    "react": "18.1.0",
    "react-dom": "18.1.0",
    "react-native": "0.70.5",
    "react-native-animatable": "^1.3.3",
    "react-native-bouncy-checkbox": "^3.0.6",
    "react-native-gesture-handler": "^2.8.0",
    "react-native-linear-gradient": "^2.6.2",
    "react-native-paper": "^5.0.1",
    "react-native-reanimated": "~2.12.0",
    "react-native-safe-area-context": "^4.4.1",
    "react-native-screens": "~3.18.0",
    "react-native-web": "~0.18.7"

You can do a hit and trial on the package version and test your app on https://browserstack.com/ before publishing on the play store. Hope it helps

neel132 commented 1 year ago

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

blinkinglight commented 1 year ago

install react-native-screens and react-native-safe-area-contex

damroyan commented 1 year ago

install react-native-screens and react-native-safe-area-contex

And? )

arshad0786 commented 1 year ago

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.jni.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:264) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228) at java.lang.Thread.run (Thread.java:923)

alfonsosn commented 1 year ago

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

crisdeoliveira commented 1 year ago

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!

cris-deoliveira commented 1 year ago

.

amjadbouhouch commented 1 year ago

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)
lufercampos commented 1 year ago

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)`
wfcwoody commented 1 year ago

Same here.

We currently have app installed on 201 devices. 96% of crashes happen on just 6 devices - all Samsung (2 x Z-Fold3, Z-Fold4, S22, A70, A71) all running Android 13 except the A70 (Android 11). Crash rate per device is between 1 and 2 crashes per day.

RN 0.70.5 EXPO 47

wfcwoody commented 1 year ago

In https://github.com/facebook/react-native/issues/33916#issuecomment-1407013982 alfonsosn said:

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

Our app isn't using react-native-date-picker (but of course react-native-date-picker may share dependencies with packages we do use)

swaroopbutala commented 1 year ago

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

image
swaroopbutala commented 1 year ago

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

image

Happening on both Android 12/13 and different devices

image
wfcwoody commented 1 year ago

We were seeing this error. Didn't see this issue in development mode. Only saw it on Samsung devices. Only about 5% of app users saw the problem.

Looking through the reports here, I had my suspicions that this was a generic error message and the causes might be varied. I rebuilt my app integrated with Bugsnag (https://www.bugsnag.com/ - I'm not affiliated with them). The next time I got one of these crashes, in Play Developer Console I saw...

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)

...but in Bugsnag I saw...

TypeError · Cannot read property 'trim' of undefined

...the cause in my case was a String.prototype.trim() being applied to an uninitialised variable. I gave the variable an initial value of "" and the problem went away. Not sure why we only saw it on certain devices.

I suspect that the way to resolve these crashes is to integrate some kind of bug catcher to get a better crash report.

hallysonmirandagipsyy commented 1 year ago

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?

wfcwoody commented 1 year ago

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 (https://github.com/facebook/react-native/issues/33916#issuecomment-1447760823) 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.

KolissnikBogdan commented 1 year ago

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).

image

ArlanBiati commented 1 year ago

Up +

Same error happening to me :(

wfcwoody commented 1 year ago

Up +

Same error happening to me :(

See https://github.com/facebook/react-native/issues/33916#issuecomment-1452077256 and https://github.com/facebook/react-native/issues/33916#issuecomment-1447760823

aspidvip commented 1 year ago

me to

zoobibackups commented 1 year ago

me too

AFDHAL2009 commented 1 year ago

Hi ,I have also same issue when i published released prod withe these devices:d'attributs : [samsung a13x (Galaxy A13 5G)] image

(https://play.google.com/console/u/1/developers/7577112937432253232/app/4974945333523670164/vitals/crashes/fffaa0613407aa21b7eec0f9822d2516/details?installedFrom=PLAY_STORE&days=28#) Android 12 (SDK 31) and this Exception com.facebook.react.common.JavascriptException: at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:79) 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:938) 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:226) at android.os.Looper.loop (Looper.java:313) at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226) at java.lang.Thread.run (Thread.java:1012)

this list dependecies:

"dependencies": { "@babel/plugin-proposal-decorators": "^7.8.3", "@react-native-clipboard/clipboard": "^1.10.0", "@react-native-community/art": "^1.1.2", "@react-native-community/async-storage": "^1.7.1", "@react-native-community/checkbox": "^0.4.2", "@react-native-community/datetimepicker": "^3.4.3", "@react-native-community/masked-view": "^0.1.6", "@react-native-community/netinfo": "^5.5.1", "@react-native-community/push-notification-ios": "^1.7.5-beta.0", "@react-native-community/toolbar-android": "0.1.0-rc.2", "@react-native-community/viewpager": "^4.1.6", "@react-native-firebase/app": "6.7.1", "@react-native-firebase/firestore": "^6.4.0", "@react-native-firebase/messaging": "6.7.1", "@react-native-firebase/storage": "6.4.0", "@react-native-picker/picker": "^1.9.8", "@types/validatorjs": "^3.15.0", "axios": "^0.19.2", "byoskill-react-native-phone-input": "^0.2.6", "email-validator-net": "^2.0.9", "geolib": "^3.3.1", "lottie-react-native": "^3.5.0", "mobx": "^5.15.2", "mobx-react": "^6.1.4", "moment": "^2.24.0", "moment-timezone": "^0.5.32", "native-base": "^2.13.14", "phone-validator-net": "^2.0.9", "popup-ui": "^1.0.10", "react": "16.9.0", "react-devtools": "^4.6.0", "react-native": "^0.62.0", "react-native-animatable": "^1.3.3", "react-native-appearance": "^0.3.4", "react-native-autocomplete-input": "^4.2.0", "react-native-background-geolocation": "^4.9.4", "react-native-background-timer": "^2.4.1", "react-native-countdown-circle-timer": "^2.3.11", "react-native-country-picker-modal": "^2.0.0", "react-native-credit-card-input": "^0.4.1", "react-native-device-info": "^10.0.2", "react-native-dropdown-autocomplete": "^1.0.18", "react-native-elements": "^2.3.2", "react-native-event-listeners": "^1.0.7", "react-native-extra-dimensions-android": "^1.2.5", "react-native-fix-image": "^2.1.0", "react-native-flatlist-slider": "^1.0.6", "react-native-geocoding": "^0.4.0", "react-native-geolocation-service": "^4.0.0", "react-native-gesture-handler": "^1.5.3", "react-native-get-location": "^1.4.3", "react-native-gifted-chat": "^0.16.3", "react-native-google-places-autocomplete": "^1.6.1", "react-native-i18n": "^2.0.15", "react-native-image-picker": "^2.3.1", "react-native-image-resizer": "^1.4.0", "react-native-indicator": "^1.2.0", "react-native-input-spinner": "^1.2.10", "react-native-keep-awake": "^4.0.0", "react-native-linear-gradient": "^2.5.6", "react-native-map-link": "^2.9.3", "react-native-maps": "0.27.1", "react-native-maps-directions": "^1.8.0", "react-native-modal": "^11.5.4", "react-native-modal-datetime-picker": "^9.1.0", "react-native-modalize": "^2.0.6", "react-native-multiple-select": "^0.5.6", "react-native-onesignal": "^4.0.3", "react-native-otp-inputs": "^7.4.0", "react-native-phone-number-input": "^2.1.0", "react-native-popup-dialog": "^0.18.3", "react-native-progress-wheel": "^1.0.5", "react-native-rate": "^1.2.12", "react-native-ratings": "^7.3.0", "react-native-reanimated": "^1.13.4", "react-native-safe-area-context": "^0.6.2", "react-native-safe-area-view": "^1.0.0", "react-native-screens": "^2.0.0-alpha.31", "react-native-scrollable-tab": "^1.0.13", "react-native-scrollable-tab-view": "^1.0.0", "react-native-select-multiple": "^2.1.0", "react-native-share": "^4.1.0", "react-native-simple-radio-button": "^2.7.4", "react-native-splash-screen": "^3.2.0", "react-native-svg": "^10.0.0", "react-native-swipe-gestures": "^1.0.5", "react-native-swiper": "^1.6.0-rc.3", "react-native-swiper-flatlist": "^2.0.4", "react-native-switch-selector": "^2.0.5", "react-native-tab-view": "^2.15.2", "react-native-text-input-mask": "^2.0.0", "react-native-toast-message": "^1.3.4", "react-native-vector-icons": "^6.6.0", "react-native-version-check": "^3.4.2", "react-native-webview": "^8.2.1", "react-navigation": "^4.0.10", "react-navigation-drawer": "^2.3.3", "react-navigation-stack": "^2.0.16", "realm": "^6.0.4", "rn-progress-loader": "^1.0.8", "rn-swipe-button": "^1.3.3", "rn-swipeable-panel": "^1.0.27", "rn-toggle-switch": "git+https://github.com/NcirImen/react-native-toggle-switch.git", "shortid": "^2.2.15", "toggle-switch-react-native": "^2.1.0", "typescript": "^3.7.5", "validatorjs": "^3.18.1" }, need helping and thanks

rjsdnql123 commented 1 year ago

me too