Some users of my app are reporting a crash related with this library
See original GitHub issueDescription
My app works on many devices but some users are reporting a crash with the following stack trace:
java.lang.IllegalStateException:
at com.swmansion.gesturehandler.react.RNGestureHandlerEnabledRootView.initialize (RNGestureHandlerEnabledRootView.java:51)
at com.swmansion.gesturehandler.react.RNGestureHandlerModule$2.execute (RNGestureHandlerModule.java:605)
at com.facebook.react.uimanager.UIViewOperationQueue$UIBlockOperation.execute (UIViewOperationQueue.java:573)
at com.facebook.react.uimanager.UIViewOperationQueue$1.run (UIViewOperationQueue.java:908)
at com.facebook.react.uimanager.UIViewOperationQueue.flushPendingBatches (UIViewOperationQueue.java:1019)
at com.facebook.react.uimanager.UIViewOperationQueue.access$2600 (UIViewOperationQueue.java:47)
at com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded (UIViewOperationQueue.java:1079)
at com.facebook.react.uimanager.GuardedFrameCallback.doFrame (GuardedFrameCallback.java:29)
at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame (ReactChoreographer.java:175)
at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame (ChoreographerCompat.java:85)
at android.view.Choreographer$CallbackRecord.run (Choreographer.java:1029)
at android.view.Choreographer.doCallbacks (Choreographer.java:854)
at android.view.Choreographer.doFrame (Choreographer.java:785)
at android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:1016)
at android.os.Handler.handleCallback (Handler.java:914)
at android.os.Handler.dispatchMessage (Handler.java:100)
at android.os.Looper.loop (Looper.java:225)
at android.app.ActivityThread.main (ActivityThread.java:7564)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:950)
This particular stack trace comes from a Redmi Note 8 device with Android 10
Platforms
- iOS
- [X ] Android
- Web
Expected behavior
I expect my app to work without crash reports related to this library
Snack or minimal code example
https://drive.google.com/drive/folders/1-16dBEGmHfM9k1lwnQSUTG_XVLY17OSH?usp=sharing
Package versions
- React: 17.0.1
- React Native: 0.64.3
- React Native Gesture Handler: ~2.1.0
- React Native Reanimated: ~2.3.1
Issue Analytics
- State:
- Created a year ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Diagnosing issues using crash reports and device logs
Crash reports describe how your app terminated, and document the code running on ... Some issues, such as problems installing an app, can...
Read more >Detect and diagnose crashes - Android Developers
When an app crashes, Android terminates the app's process and displays a dialog to let the user know that the app has stopped, ......
Read more >An easy way to collect crash reports in our Android libraries
When the library is integrated to a third party app and crashes, that crash ... of users where they use their sdk and...
Read more >Get started with Firebase Crashlytics - Google
This quickstart describes how to set up Firebase Crashlytics in your app with the Firebase Crashlytics SDK so that you can get comprehensive...
Read more >Reading Live Crash Reports - Ableton
Identifying the specific process underway at the time of a crash may ... macOS: Macintosh HD/Users/[Username]/Library/Preferences/Ableton/Live x.x.x/Log.txt ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes,
RNGestureHandlerEnabledRootView
was the cause of many crashes, and it was deprecated in version 2.0 in favor of<GestureHandlerRootView>
, so we decided to remove it as part of logic it required was executed even if it was unused. We figured that throwing an exception with instructions when it was initialized was the best way to ensure that the information reaches the people still using it.That Flipper log, isn’t giving much to go after. Could you give some more details: