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

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 <unknown>@99:13818 Pe@99:90199 Re@99:13478 Ie@99:13664 receiveTouches@99:14448 value@40:3544 <unknown>@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

[siddesh94]

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

[hassey13]

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.