JS bundle regresses to the one bundled with the app, if no connection

When failing to load updated JS bundle on slow connection, app regresses to the very first JS bundled and gets stuck with that JS version before the next exp publish.

Example: binary was released with JS v1, then new code was pushed several times and new JS is v30. User has problem downloading JS v31, the app is stuck with JS v1, before the next JS update.

Is there a way to load the last successfully downloaded version of the JS bundle instead?

1 Like

Hi @andrey - really sorry you’re experiencing this, this is definitely not the intended behavior. Could you post your app.json, and also, which platform is this happening on? Finally, could you go into a bit more detail about what happens when loading the bundle fails? Does it try to download and wait a while before timing out and falling back to the older version?

Hi @esamelson, thanks for your reply. Yeah, it shows splash screen, waits till timeout, then loads the older version. Happens on iOS, haven’t checked Android yet.

  "expo": {
    "name": "",
    "description": "",
    "slug": "",
    "privacy": "public",
    "sdkVersion": "28.0.0",
    "platforms": ["ios", "android"],
    "version": "1.0.0",
    "orientation": "portrait",
    "icon": "./assets/images/icon.png",
    "splash": {
      "image": "./assets/images/splash.png",
      "resizeMode": "contain",
      "backgroundColor": "#ffffff"
    "updates": {
      "fallbackToCacheTimeout": 15000
    "assetBundlePatterns": [
    "ios": {
      "supportsTablet": true,
      "bundleIdentifier": "",
      "buildNumber": "2",
      "config": {
        "usesNonExemptEncryption": false
    "android": {
      "package": "",
      "versionCode": 2,
      "permissions": [
    "androidStatusBar": {
      "barStyle": "light-content",
      "backgroundColor": "#999999"

Hi @andrey - thanks very much for reporting this. We’ve been able to repro – it seems like it only happens intermittently when there is an error in the middle of downloading a new version. We’re working on a fix and hope to have it ready soon.

Awesome, thanks!

Hey @andrey - sorry for the slow update here. I’ve landed a fix internally for this which will go out at the time of our next release, SDK 29. This should be soon – hopefully within the next week. You can watch our blog as we will announce there when it’s out.

Thanks again for reporting this; we really appreciate it!


Awesome, Thank you!

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.