App crashes with SIGABRT #1912
Labels
Comments
Issue validatorThe issue is valid! |
|
Hey @heroic. Is it your application? |
|
@piaskowyk yes |
|
I'm also experiencing this with RN 0.64.0, react-native-reanimated 2.0.1, gradle 6.7, gradle tools 4.1.3, AS 4.1.3. I'm forcing fb soloader like this: and getting this crash on a Pixel3 |
1 task
|
``Recently, we at @queimadiaria pushed your new app to production and started to see this same error being catch with Sentry. It's happening a lot with Motorola phones (which is very popular in Brazil).
We are seeing some UnknowCppException too. |
|
Samsung here |
|
hi there seems we're having the same issue, our device catch this error RN: 0.64.2 |
|
Seeing similar crashes: moto e (XT2052DL) RN 0.64.0 |
|
+1 |
|
I use React Native 0.63.4 and React Native Reanimated 2.2.4, and I got almost similar stack traces. The crash might not be related to any of the crashes above, but I hope that this fix will at least help somebody. Click here to see my full stack traces |
|
Seeing this on Android (real devices and emulators) in both debug and release mode when restarting the JS bundle. "react-native-reanimated": "2.2.3" |
What is your current version after the upgrade? |
My React Native version stays the same at 0.63.4. I only upgrade its dependencies. "dependencies": {
"react-native": "0.63.4",
} |
|
Hello @Looooong @kirildobrev919 @heroic @jesseproudman @mutablestudio @mgambati @ecauende @rinoarmadiaz @Only-IceSoul Did you manage to fix the issue, is it still happening for you? Did any one of you manage to create a repro for this issue? Did you clear caches, all of them that are possible to clear? Thank you for circling back to me if you can, and have a nice day 😊 |
jkadamczyk
added
the
Close when stale
|
From our team @nhannah took over the issue. Will ping him. |
github-actions
bot
removed
the
Close when stale
I had the error with react navigation, I set animation to true, I no longer have problems |
|
@Only-IceSoul where did you do this? Can you point to the docs? |
|
It is still happening for Android devices. |
|
It' still happening with RN 0.68.2 |
|
For me, it happens with ( only for Android ):
|
|
Same issue here on Android with: |
|
Same issue here on android with: |
|
Also experiencing crashes. Hermes is enabled on the project
`OS Version: Android 11 (RP1A.200720.012.A107FXXU8CVG2) Exception Type: Unknown (SIGSEGV) Application Specific Information: Thread 0 Crashed: |
|
My initial crash was I think what resolved it for me was to remove this lines in package com.swmansion.gesturehandler.react.example;
import com.facebook.react.ReactActivity;
- import com.swmansion.gesturehandler.react.RNGestureHandlerEnabledRootView;
public class MainActivity extends ReactActivity {
- @Override
- protected ReactActivityDelegate createReactActivityDelegate() {
- return new ReactActivityDelegate(this, getMainComponentName()) {
- @Override
- protected ReactRootView createRootView() {
- return new RNGestureHandlerEnabledRootView(MainActivity.this);
- }
- };
- }
}Other things I did that might have solved the issue :
I really feel like the edition of |
|
Maybe I was wrong, or at least there is a second problem. The following code works (my app is fully functional): On the other hand, the following causes the This happens with the following packages versions: The complete crash log is quite uninformative but here it is just in case someone sees something: |
|
Further investigations lead me to a somewhat unrelated thread (different crash with drawer) that advises to use the const Drawer = createDrawerNavigator<DrawerParamList>();
function DrawerNavigator() {
return (
<Drawer.Navigator
+ useLegacyImplementation
>
<Drawer.Screen name="BottomTabs" component={BottomTabs} />
</Drawer.Navigator>
);
}
export function RootNavigator() {
return (
<NavigationContainer>
<DrawerNavigator />
</NavigationContainer>
);
} |
|
I have this error. The underlying cause is: |
|
Fixed it on my codebase. removed a NativeViewGestureHandler from my react dom. - provided by 'react-native-gesture-handler' |
|
For me, the source of the crash is I am forgetting to import the Bundle in MainActivity.java |
In my case, it was a system crash from a missing Android Bluetooth permission during the animation. I find it using a setTimeout function to make sure the animation finishes. |
|
I get a similar message in my expo dev client on startup: it points to this: with v2.14.4 |
|
It happens when App was reloaded in JSContext(restart by react-native-codepush, react-native-exit-app, ...etc) and EventHandler was not clear (it keeps Java mNodesManager listener but in Cpp was destroyed). It should be clear when NativeProxy was destroyed. Maybe it was fixed in the latest release. If not, ping me then I will send a PR. |
This was referenced Mar 1, 2023
|
@kyunkakata Thanks for putting me on the right track! Patch for 2.x users (like me 🙃 ) |
|
How did you apply that patch @pepf? |
|
@spsaucier Basically I applied the fix from the comment I refered to using patch-package, no changes to the contents. This did the trick for me in terms of backporting this fix for 2.x. But we're quite eager to upgrade to 3.x since there's still some unexplainable crashes happening 😅 |
|
I have not found that the patch prevents this error, unfortunately. |
|
The solution is to upgrade your Reanimated to newer version. Please use Reanimated 3. |
|
Im using reanimated Any suggestions to get this one fixed? affecting 16% of our user base imo this is still an issue and should be reopened |
|
I have the same issue |
|
Same issue, crashes on every second hot reload in dev mode on Android with an error: Dependencies are: |
|
Getting this issue with reanimated |
|
Getting this issue with reanimated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Description
For some users using vivo, OPPO, Xiaomi, or Samsung phones, we are seeing a crash in the native code.
Expected behavior
App should not crash or at least stacktrace should point to the error in the JS land, to allow for debugging.
Actual behavior & steps to reproduce
App crashes randomly.
Snack or minimal code example
We haven't found a way to replicate this on any of our test devices.
Package versions
Affected platforms
The text was updated successfully, but these errors were encountered: