Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

expo-updates crash on bare workflow

See original GitHub issue

🐛 Bug Report

Environment

Expo 37, expo-updates 0.2.5. Android Q.

Steps to Reproduce

I have a bare react native app, ejected from expo some time ago. I have added expo-updates following the instructions.

Everything works ok when I run react-native run-android --variant=release, the app works properly.

Then I do expo publish to create a new update.

When the app start, it just crashes and get closed. From adb logcat:

05-31 19:16:45.190 31901 31959 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
05-31 19:16:45.190 31901 31959 E AndroidRuntime: Process: com.discovmobile, PID: 31901
05-31 19:16:45.190 31901 31959 E AndroidRuntime: com.facebook.react.common.JavascriptException: Error: The Expo SDK requires Expo to run. It appears the native Expo modules are unavailable and this code is not running on Expo. Visit https://docs.expo.io to learn more about developing an Expo project., stack:
05-31 19:16:45.190 31901 31959 E AndroidRuntime: <unknown>@13:185
05-31 19:16:45.190 31901 31959 E AndroidRuntime: v@2:1474
05-31 19:16:45.190 31901 31959 E AndroidRuntime: <unknown>@9:67
05-31 19:16:45.190 31901 31959 E AndroidRuntime: v@2:1474
05-31 19:16:45.190 31901 31959 E AndroidRuntime: <unknown>@8:191
05-31 19:16:45.190 31901 31959 E AndroidRuntime: v@2:1474
05-31 19:16:45.190 31901 31959 E AndroidRuntime: <unknown>@6:48
05-31 19:16:45.190 31901 31959 E AndroidRuntime: v@2:1474
05-31 19:16:45.190 31901 31959 E AndroidRuntime: d@2:876
05-31 19:16:45.190 31901 31959 E AndroidRuntime: global code@1352:4
05-31 19:16:45.190 31901 31959 E AndroidRuntime:
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:71)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:371)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:150)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:883)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:100)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:237)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225)
05-31 19:16:45.190 31901 31959 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:919)

Expected Behavior

I expect the app to update its bundle without problems. I don’t know why the app in its variant release needs the expo cli to work, it seems not to need it if I do react-native run-android --variant=release.

I’m using this other packages from expo:

    "expo": "^37.0.0",
    "expo-asset": "^8.1.5",
    "expo-constants": "~9.0.0",
    "expo-task-manager": "~8.1.0",
    "expo-updates": "^0.2.5",

Actual Behavior

The app can’t be used anymore. Need to uninstall and move it to the phone using react-native cli again.

Reproducible Demo

https://github.com/arqex/otaTestApp

Issue Analytics

State:
Created 3 years ago
Comments:19 (9 by maintainers)

Top GitHub Comments

1reaction

dineshmattacommented, Jun 3, 2020

Hey @brentvatne its working for me, I compared the diff from the new project and I fixed mine.Thanks for the suggestion.

0reactions

byCedriccommented, Aug 7, 2020

Hey people! I can confirm this issue is related to expo-cli@<=3.23.2. This should be fixed in the latest CLI (3.23.3) 🚀 Please try that one and open a new issue when this happens again. Sorry for the inconvenience!

This issue is the same one as https://github.com/expo/expo/issues/9572 and was fixed with https://github.com/expo/expo-cli/issues/2426.

Top Results From Across the Web

expo-updates crashes the app in Release build on RN 0.70 ...

Summary installing expo-updates on a bare RN project crashes the app on Release build on iOS. No extra config, just bare minimum installation....

Error recovery - Expo Documentation

If there is no new update, the update finishes downloading, or the timer runs out (whichever happens first), the app will throw the...

APK created using EAS-CLI crashing on physical device ...

I am using Expo bare workflow for creating the react-native app. The App development and testing are working perfectly on IOS.

Rolling back from bare workflow expo App : r/reactnative

Hi everyone! While trying to make Facebook login in my fully managed react native expo App, I tried to install this library ...

Monitor your React Native application

Our agent collects crash data, network traffic, and other information for hybrid ... Integration with Expo is automatic with bare workflow but requires...