You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Old Bundle Used After App Update from App Store/Google Play
Scenario:
The app is released with version 1.0.0.
Users of version 1.0.0 receive an Over-the-Air (OTA) update, which delivers a new bundle.
A new app version 1.0.1 is built and released to the App Store/Google Play without any OTA update. The default bundle embedded in version 1.0.1 is newer than the OTA bundle from version 1.0.0.
Problem:
When a user updates the app from version 1.0.0 to 1.0.1 via the App Store or Google Play:
The app continues to use the old OTA bundle from version 1.0.0 that was downloaded previously.
The default bundle embedded in version 1.0.1, which is newer than the old OTA bundle, is not used.
This issue does not occur for users downloading version 1.0.1 for the first time, as they start with the default bundle of version 1.0.1.
Expected Behavior:
When a user updates the app from version 1.0.0 to 1.0.1, the app should:
Use the default bundle of version 1.0.1 if it is newer than the cached OTA bundle of version 1.0.0.
Alternatively, use the latest OTA bundle of version 1.0.1 if available.
Temporary Solution:
Before releasing version 1.0.1 to the App Store or Google Play:
Publish the OTA update for version 1.0.1.
When the user updates to version 1.0.1 and opens the app, it will download the new OTA bundle for 1.0.1, ensuring they are using the latest version.
Assumption api design like this:
Design the OTA API to filter bundles based on the app version (e.g., 1.0.0, 1.0.1). The app should only receive OTA updates compatible with its specific version.
The text was updated successfully, but these errors were encountered:
Issue: Old Bundle Used After App Update from App Store/Google Play
Scenario:
1.0.0
.1.0.0
receive an Over-the-Air (OTA) update, which delivers a new bundle.1.0.1
is built and released to the App Store/Google Play without any OTA update. The default bundle embedded in version1.0.1
is newer than the OTA bundle from version1.0.0
.Problem:
When a user updates the app from version
1.0.0
to1.0.1
via the App Store or Google Play:1.0.0
that was downloaded previously.1.0.1
, which is newer than the old OTA bundle, is not used.1.0.1
for the first time, as they start with the default bundle of version1.0.1
.Expected Behavior:
When a user updates the app from version
1.0.0
to1.0.1
, the app should:1.0.1
if it is newer than the cached OTA bundle of version1.0.0
.1.0.1
if available.Temporary Solution:
Before releasing version
1.0.1
to the App Store or Google Play:1.0.1
.1.0.1
and opens the app, it will download the new OTA bundle for1.0.1
, ensuring they are using the latest version.Assumption api design like this:
1.0.0
,1.0.1
). The app should only receive OTA updates compatible with its specific version.The text was updated successfully, but these errors were encountered: