react-native icon indicating copy to clipboard operation
react-native copied to clipboard

Crash on Android with DevSupportException

Open arjun1194 opened this issue 2 years ago • 2 comments

Description

Getting Crash on android with the following stack trace

java.lang.RuntimeException: 
  at com.facebook.react.bridge.DefaultNativeModuleCallExceptionHandler.handleException (DefaultNativeModuleCallExceptionHandler.java:20)
  at com.facebook.react.devsupport.DisabledDevSupportManager.handleException (DisabledDevSupportManager.java:178)
  at com.facebook.react.bridge.CatalystInstanceImpl.onNativeException (CatalystInstanceImpl.java:629)
  at com.facebook.react.bridge.CatalystInstanceImpl.access$1100 (CatalystInstanceImpl.java:47)
  at com.facebook.react.bridge.CatalystInstanceImpl$NativeExceptionHandler.handleException (CatalystInstanceImpl.java:647)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:29)
  at android.os.Looper.loop (Looper.java:223)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226)
  at java.lang.Thread.run (Thread.java:919)
Caused by: com.facebook.react.devsupport.JSException: 
  at com.facebook.react.bridge.CatalystInstanceImpl.onNativeException (CatalystInstanceImpl.java:629)
  at com.facebook.react.bridge.CatalystInstanceImpl.access$1100 (CatalystInstanceImpl.java:47)
  at com.facebook.react.bridge.CatalystInstanceImpl$NativeExceptionHandler.handleException (CatalystInstanceImpl.java:647)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:29)
  at android.os.Looper.loop (Looper.java:223)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:226)
  at java.lang.Thread.run (Thread.java:919)

Version

0.67.4

Output of npx react-native info

System:
    OS: macOS 12.2
    CPU: (8) arm64 Apple M1
    Memory: 1.36 GB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.5.0 - /usr/local/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.11.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK: Not Found
    Android SDK:
      API Levels: 23, 28, 29, 30, 31, 32
      Build Tools: 27.0.3, 28.0.3, 29.0.0, 29.0.3, 30.0.2, 30.0.3, 31.0.0
      System Images: android-24 | ARM 64 v8a, android-24 | Google APIs ARM 64 v8a, android-25 | Google APIs ARM 64 v8a, android-27 | ARM 64 v8a, android-30 | ARM 64 v8a, android-30 | Google APIs ARM 64 v8a, android-30 | Google Play ARM 64 v8a, android-31 | ARM 64 v8a, android-31 | Google APIs ARM 64 v8a, android-31 | Google Play ARM 64 v8a
      Android NDK: 22.1.7171670
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: /undefined - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.13 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce

I have seen this crash on play console and was not able to reproduce it, but it happens 100% of the time in foreground. 99% of the time it happens on a REDMI / XIAOMI phone and it only happens on android 9, 10, 11

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

I dont have a code example that would be helpful

arjun1194 avatar Jul 26 '22 18:07 arjun1194

This is happening to my app in production after upgrading to RN 0.69 (Expo 46). Lots of crashes on devices running Android > 10.

kylerjensen avatar Aug 26 '22 15:08 kylerjensen

Same issue, same steps only that mine fails on realme 7 android 11

jerryOluranti avatar Nov 07 '22 10:11 jerryOluranti

Any news about thtat? I encountered the same problem

red-made avatar Jan 20 '23 10:01 red-made

Same issue, same steps only that mine fails on Samsug devices with android 11,12,13

nerdytrustdeveloper avatar Jun 02 '23 00:06 nerdytrustdeveloper

Hey, We're cleaning up the React Native issue tracker to make sure we focus on the most important issues first.

I'm closing this one because it's stale and related to a version of React Native we no longer support. If the issue persists on the latest version, please re-open a new issue and reference this one.

Moreover, we generally can't fix issues just by looking at a stacktrace reported from your crash reporting platform. Please provide a reproducer in your future reports.

Thank you.

cortinico avatar Dec 04 '23 12:12 cortinico