Fatal Exception: java.lang.RuntimeException

Firebase Crashlitics error in standalone application

Fatal Exception: java.lang.RuntimeException: Expo encountered a fatal error: Attempting to call JS function on a bad application bundle: RCTDeviceEventEmitter.emit()
at host.exp.exponent.experience.BaseExperienceActivity.lambda$consumeErrorQueue$0(BaseExperienceActivity.java:204)
at host.exp.exponent.experience.-$$Lambda$BaseExperienceActivity$zZZNiLUhJmY4AlwF2loJATXcbqc.run(-.java:2)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:237)
at android.app.ActivityThread.main(ActivityThread.java:8016)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1076)


Expo CLI 3.27.4 environment info:
OS: Windows 10 10.0.18362
Node: 12.18.2 -xxxxxxxx\nodejs\node.EXE
npm: 6.14.8 - xxxxxxx\AppData\Roaming\npm\npm.CMD
expo: ^38.0.9 => 38.0.10
react: 16.13.1 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2
react-navigation: ^4.4.0 => 4.4.0
Expo Workflow: managed

If the users delete Standalone app storage the app will restart an all is ok, but sometimes after a path in some devices we get this crash and the app dont run till the storage is not cleared.

I am also getting exactly the same error on expo sdk 39, I am on managed workflow and firebase crashlytics is not being used, I only have expo-firebase-core and expo-firebase-analytics added in dependencies, are you sure its a firebase crashlytics error? I am also trying to solve it but have no clues where to look for as firebase-crashlytics requries bare workflow to work and I don’t want to eject just yet.