Code Push release crashes android app after downloading new bundle, rollbacks.

[fariskhan563]

Our production android app is crashing after every new code push update, it downloads the updated bundle and right after while installing and restarting the app it crashes the android app, upon again opening the app it just rollbacks.

The problem is I myself is not able to reproduce it, as it is working in staging and also if I a create a .apk with production .env and try in simulator it works just fine, but it crashes on the production app bundle .aab which is download and installed using Google Play Store.

Crash info given by Firebase Crashlytics.

 Crashed: Thread :  SIGABRT  0x0000000000000000
#00 pc 0x831f0 libc.so 
#01 pc 0x831c0 libc.so 
#02 pc 0x4b9e5c libart.so 
#03 pc 0xb458 libbase.so 
#04 pc 0x3781f8 libart.so 
#05 pc 0x389d54 libart.so 
#06 pc 0x12b888 libreanimated.so 
#07 pc 0x129440 libreanimated.so 
#08 pc 0x1444a4 libreanimated.so 
#09 pc 0x1504f4 libreanimated.so 
#10 pc 0x1503c4 libreanimated.so 
#11 pc 0x150314 libreanimated.so 
#12 pc 0x1502b0 libreanimated.so 
#13 pc 0x14ef50 libreanimated.so 
#14 pc 0x162050 libreanimated.so 
#15 pc 0x161f10 libreanimated.so 
#16 pc 0x161cd0 libreanimated.so 
#17 pc 0x1616e4 libreanimated.so 
#18 pc 0x1617b4 libreanimated.so 
#19 pc 0x161548 libreanimated.so 
#20 pc 0x1614f8 libreanimated.so 
#21 pc 0x77d38e5eb4  
#22 pc 0x77d54d634a  
#23 pc 0x77d54dbadf  
#24 pc 0x77d54dbadf  
#25 pc 0x592d18 libart.so 
#26 pc 0x77d4f124f0  
#27 pc 0x77d4f124f0  
#28 pc 0x77d4f124f0  
#29 pc 0xa418dc boot-framework.oat 
#30 pc 0x5c7064 libart.so 
#31 pc 0x77d54dbadf  
#32 pc 0x140468 libart.so 
#33 pc 0x140468 libart.so 
#34 pc 0x2197fd8 boot-framework.oat 
#35 pc 0x2197e80 boot-framework.oat 
#36 pc 0x25601e4 boot-framework.oat 
#37 pc 0x591cbc libart.so 
#38 pc 0x16c1c94 boot-framework.oat 
#39 pc 0x25651cc boot-framework.oat 
#40 pc 0x2193b7c boot-framework.oat 
#41 pc 0x214ccd8 boot-framework.oat 
#42 pc 0x214d494 boot-framework.oat 
#43 pc 0x27d388 boot.oat 
#44 pc 0x24d33c8 boot-framework.oat 
#45 pc 0x16b23ec boot-framework.oat 
#46 pc 0x16bba24 boot-framework.oat 
#47 pc 0xcb7644 boot-framework.oat 
#48 pc 0x5cdffc libart.so 
#49 pc 0x1375b8 libart.so 
#50 pc 0x14600c libart.so 
#51 pc 0x4b171c libart.so 
#52 pc 0x59184c libart.so 
#53 pc 0x5cdffc libart.so 
#54 pc 0x4b32c0 libart.so 
#55 pc 0x6d4b44 boot.oat 
#56 pc 0x6d8b58 boot.oat 
#57 pc 0x231d9c0 boot-framework.oat 
#58 pc 0x231d58c boot-framework.oat 
#59 pc 0x2339b98 boot-framework.oat 
#60 pc 0x387628 boot-core-libart.oat 
#61 pc 0x233b8b8 boot-framework.oat 
#62 pc 0x43e520 libart.so 
#63 pc 0x43e558 libart.so

Crash info given by Sentry.

system
exception
stack-trace
frame
functionfacebook::jni::detail::MethodWrapper<T>::call
frame
function_ZN8facebook3jni6detail15FunctionWrapperIPFvNS0_9alias_refIPNS1_8JTypeForINS0_11HybridClassIN10reanimated12EventHandlerENS1_15BaseHybridClassEE8JavaPartENS0_7JObjectEvE11_javaobjectEEEONS3_INS0_7JStringEEEONS3_INS_5react11WritableMapEEEESE_vJSH_SL_EE4ca...
frame
function_ZN8facebook3jni6detail22CallWithJniConversionsIPFvNS0_9alias_refIPNS1_8JTypeForINS0_11HybridClassIN10reanimated12EventHandlerENS1_15BaseHybridClassEE8JavaPartENS0_7JObjectEvE11_javaobjectEEEONS3_INS0_7JStringEEEONS3_INS_5react11WritableMapEEEEvSE_JSH_S...
frame
function_ZN8facebook3jni6detail13MethodWrapperIMN10reanimated12EventHandlerEFvNS0_9alias_refINS0_7JStringEEENS5_INS_5react11WritableMapEEEEXadL_ZNS4_12receiveEventES7_SA_EES4_vJS7_SA_EE8dispatchENS5_IPNS1_8JTypeForINS0_11HybridClassIS4_NS1_15BaseHybridClassEE8J...
frame
functionreanimated::EventHandler::receiveEvent
frame (marked out of app by stack trace rule (family:native function:std::* -app))
functionstd::__ndk1::function<T>::operator()
frame
functionfacebook::jni::JObject::getClass
frame
function_JNIEnv::GetObjectClass
frame
functionart::JavaVMExt::JniAbort
frame
functionandroid::base::LogMessage::~LogMessage
frame
functionart::Runtime::Abort
frame
functionabort

I've disabled the update from the console so that users don't face this crash.

Environment

• react-native-code-push version: "^7.0.4"
• react-native version: "0.67.4"
• iOS/Android/Windows version: Android Version:10
• Does this reproduce on a debug build or release build? - Release
• Does this reproduce on a simulator, or only on a physical device? - Physical Device

[thitoo-yf]

same problem. any update?

[fariskhan563]

Still not able to find the cause or fix it, and waiting for anyone to help on this thread :/

[Gabriel-Mariano]

Alguém conseguiu solucionar o problema?

[cjanietz]

I am encountering the same issue Here is a fully symbolicated stack trace

[swizes]

I think one of the following things are causing this

• Hermes
• RN-GestureHandler
• React-native-screens

[ra1nj]

I think this causes the rollback , after I config project.ext.react = [ enableHermes: false, ] and release CodePush without Hermes, solved the problem; Any other solutions do not need to turn off Hermes ?

[Acetyld]

Any update?

After lots of debugging, a new project with hermes enabled is only thing that works. Hermes disabled causes above error.

[claudesortwell]

@Acetyld So having hermes enabled didnt cause the above error? Wondering if we should enable Hermes because we are getting the above error

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[firehand33]

Same problem..any solution beside enable hermes?

[alberto-instnt]

Had to disable Hermes to make it work.

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[microsoft-github-policy-service[bot]]

This issue will now be closed because it hasn't had any activity for 15 days after stale. Please feel free to open a new issue if you still have a question/issue or suggestion.