I’ve noticed an issue with the native app builder and OTA updates.
Usually, when I push an OTA update, it works fine. However, every now and then—typically after pushing several OTA updates over a period—something breaks. The app suddenly starts building again, and when it finishes, users see the message: “It’s time to update your app”
…even though no new version is available in App Store Connect.
The only way I’ve been able to fix this is by sending a new build to the app stores.
Has anyone else experienced this? Is there something I might be doing wrong, or is this a known limitation with OTA updates?
When this happens, i can see in Bubble that its building (even when its OTA).
And when its finished “building” it gets the same version number as before, and for some reason users get asked to update the app.
Now it happent again. And this happent while i had my app to review with Apple.
I just made an OTA update.
In the attached screenshoot you can see what i see in Bubble. When this is finished “Building” all users will get an “TIme to update your app” message in the app, but there is no available updates.
The only way to make my app work again is to submit a new version and wait for it to be approved.
New build showed in bubble’s mobile settings in “building…” status
Build dissapeared from bubble settings
Opened live app, it crashed
Opened again and it said “it’s time to update your app in app store”
Navigated to app store and there’s no option to update
Clicked “Open” in app store and it brought me back to “it’s time to update your app page”
Users are stuck and can’t use app (I’m only user so it’s not urgent).
Not sure if it matters, the change that I shipped was minor. I replaced a WF that opened a view with a sheet that uses the share sheet plugin. Everyhting else was the same.
This is odd indeed. The update app view should only show if the live version has been deprecated. Can you please file a bug report so engineering can look into it, if you havent already?
We will launch our app on Sunday, but it feels really unsecure, if all users suddenly can get “You need to update your app”, even when there is no updates available. And everything just becouse i pushed an OTA Update.
Could anyone clearify why all users is required to update their app? Do this usally happens only when its a major update?
Its okay that we have a bug where it rebuilds the app, but its really scary that it also tells all users to update their app, and no one can open the app (becouse there is no updates available)
Screenshot where you can see that it tried to build a version already built:
After my last post i can see that it did not crash this time, it only said “building…”
But now i have a new interesting thing. I get this message when i try to look at builds.
Not critical, but im not sure if the bug might have been fixed already? So i let you know in case this is a new bug after the fix.
I did some changes yesterday (Like you can see on the screenshot). Today i wake up with an “Its time to update your app” message, and the app is not working anymore. Everything worked when i went to bed.
Update: Issue tracker for backend workflow was turned off, and i had an issue there. So i hope that caused the error. Ill update here when i know.
Update2: Still failed after backend workflow errors was fixed. I will try to deploy a major now, to see if that helps.
I attempted to push a new build but encountered an error. This version needs to be submitted for review in order to proceed with the launch, so I’d really appreciate it if someone could look into this as soon as possible.
I had to withdraw the previous version because Apple wasn’t able to test it properly while the update banner was active.
