Currently users run my app where app.json
does not specify updates
– Per your docs, this means they are receiving automatic exp publish
updates on first app load every time.
So:
-
Let’s say I have app Version1 and
exp publish
called Publish1 -
Let’s say I
exp build
a new standalone app (lets call it Version2) to disable automatic updates:
"updates": {
"checkAutomatically": "ON_ERROR_RECOVERY",
"fallbackToCacheTimeout": 0
},
And add custom logic to present a user option to Updates.reload()
-
I then
exp publish
Publish2 -
When the user downloads this Version2, according to the docs and answers from Slack, the app:
-
- Will read the new
app.json
first and
- Will read the new
-
- Still loads from Expo’s last
exp publish
- Still loads from Expo’s last
-
In that case, does this mean I have “bricked” my users into the last exp publish
Publish1? And therefore they will never be prompted for the new Publish2 which contains the Updates.reload code?