Hey team, since yesterday’s forced rebuild (the one triggered by Apple’s new agreement requirements), our live app has basically become unusable.
We currently have two build versions: 2.4.4 (the live one) and 2.6.0 (the newly generated build). The issue is that all our users are being forced to “update” to 2.6.0, even though that version isn’t available on the App Store and hasn’t been approved.
It looks like Bubble is pushing users toward a build that doesn’t exist.
Has anyone else seen this or know what’s going on?
@patrick.white what happens if you force quit the app and re-open? It’s possible the currently downloaded version doesn’t yet have the OTA’d code,. but since there is a new build, it think thats you need to update to the latest build version even though version 2.4.4 should still be supported.
Yea nope nothing worked. It basically thought my app had a published version that actually hadn’t gone through review yet. Basically made my app unusable until the new build was accepted - so just an fyi to your team.
@patrick.white an engineer took a deeper look last night and it looks like the issue was that there was actually a newer OTA live version that was deprecated than the one that was left live, which meant that any app with that code was stuck because you can’t go backwards. Do you remember deprecating the right live version after you deployed the new build?
