Updating standalone always use old JS bundle at first launch

Expo SDK
3

Hi @ccheever, thanks for the reply.

  1. My updates in app.json:
"updates": {
      "enabled": true,
      "checkAutomatically": "ON_ERROR_RECOVERY"
    },

fallbackToCache should be talking about Automatic Updates, but I have already implemented my own manual update in background. So it is not needed.

This problem (using old bundle) is not starting from sdk v27, but long long time ago. I am expecting that when a user update his app from appstore and then open it, it should be using the js bundle within the new standalone, instead of the old/cached one

  1. I have built again after seeing another reply from you, but still the same.

The whole Location package failed. The reproduction procedure is as follow:

  1. Install app of SDK v25 version
  2. Open it once and allow the permission
  3. Update it
  4. Open it and askAsync seems to be denied or undetermined (cannot confirm this in standalone, but at least I know its not grantes because of some custome logics of my own).
  5. Close app and reopen, still the same
  6. Uninstall and reinstall.
  7. Works perfectly.

My guess is: the permission granted in app based on SDK v25 is not carried onto app based on SDK v27 crashes something permanantly. And will never recover even after closing the app.

Note: These might be 2 independent issues.