Closed mhazizk closed 1 year ago
hey @mhazizk as a sanity check, could you do checkout your app to the state which you made your build, and make an additional development build.
An example of how to do this is to run eas build --profile development
while your eas.json is configured like so:
"build": {
"development": {
"developmentClient": true,
...
},
...
}
When you open the app and physically shake your phone, you should be able to see a debug view and explicitly load the problematic update:
Please report back whether you are able to load this update properly. If not, let us know:
package.json
at the time you made the buildpackage.json
at the time you made the problematic updateclosing due to inactivity
Build/Submit details page URL
No response
Summary
I set my
expo.runtimeVersion.policy = "appVersion"
with version0.8.0-alpha
and theneas build --profile production
and publish it perfectly to play store.Later on, I have a small change to update, without adding any native code, and changing
expo.runtimeVersion.policy
orapp.json
orapp.config.js
so the version is still the same0.8.0-alpha
and theneas update
toproduction
.But unfortunately, there is no update shown after restarting the app with the same version twice or more.
Currently, my
eas update
quota is not the problem.Is this the right way to update targeting specific
appVersion
? or maybe there is some fix to do it?Managed or bare?
managed
Environment
Error output
No response
Reproducible demo or steps to reproduce from a blank project