I’m facing a consistent issue with mobile OTA updates in Bubble native apps.
What’s happening:
When I push an OTA update (no new build submitted to the store), users opening the app are redirected to an “Update App” page / flow, similar to what happens when a new build is required.
However, since this is an OTA update:
-
There is no update available on the App Store / Play Store
-
Users land on a dead-end, because the store does not show any update option
-
This creates confusion and effectively blocks app usage
Expected behavior:
-
OTA updates should apply silently or via an in-app reload
-
The “Update App” redirect should trigger only when a new store build is actually required
Actual behavior:
-
OTA update triggers the same update flow as a store build
-
App opens an update screen even though the store has no update
Why this is a problem:
-
Users think the app is broken
-
There’s no way for them to proceed
-
OTA updates become risky to deploy in production
This seems like a logic mismatch between OTA versioning and store build enforcement.