Continuing the discussion from Updating with Updates API:
This seems to conflict with what’s in the docs:
Immediately reloads the current experience. This will use your app.json updates configuration to fetch and load the newest available JS supported by the device’s Expo environment. This is useful for triggering an update of your experience if you have published a new version.
Will Expo.Updates.reload() force a reload from the server, even if fallbackToCacheTimeout is set to 0?