CODEWITHSUNDEEP
react-nativeexpoexponentjs
stvn
stvn

Reputation: 51

Forcing refresh of a published Expo app

could somebody explain how the Expo client decides whether to refresh my app or use the current version cached (~already downloaded) in the client?

When I'm pushing out a new version with exp push, the Expo app (on Android) doesn't seem to pick it up, unless I clear all data of the app.

I thought that bumping the expo.version in the app.json would solve this but this doesn't seem to be the case.

Thanks!

UPDATE

Ok, I understand it is supposed to happen automatically, but this doesn't seem so - I tried multiple devices which were not offline - I suppose there must be something obvious I'm missing...

https://docs.expo.io/versions/latest/guides/offline-support.html#load-js-updates-in-the-background

Upvotes: 5

Views: 4468

Answers (2)

dmmd
dmmd

Reputation: 31

Check that you don't have this option on the app.json file:

"updates": {
    "fallbackToCacheTimeout": 0
},

I had this option in there and it prevented the app from waiting for a new version to be downloaded.

Upvotes: 3

Fixticks
Fixticks

Reputation: 51

(on Android) I succeeded by opening the app in Expo, I would see the cached version, then I force stopped the app intentionally, both the app and the expo client. This removes it from the list of open apps on the phone. Relaunched the expo client, then tapped my demo app again, and it loaded the new version. Tested a few seconds after publishing.

Upvotes: 0

Related Questions