Hello, for the past several days if I want to deploy an update to my app Bubble is requiring me to do a new build. I did it a few times last week when I was getting ready for the app store but it’s still requiring me to do a new build every time. This is blocking me from being able to test minor updates in TestFlight and I’m going to have to get reapproved in the App Store. I’m also concerned this is counting against my build limit. Is anyone else having this problem? Maybe I just need to deploy a new build but I’ve done it a few times and nothing has changed.
Can’t you run these tests in BubbleGo?
Hello, this is due and the important updates released by the bubble. In this case it is not possible to release OTA.
From what I remember, in this case the builds are not counted if they are “obligated” for updates on their part.
I’m glad to hear they’re not counted against me. I just did a new build and lo and behold, if I try to deploy again it still says I have to do a new build. It seems like Bubble has just turned off OTA updates altogether. Unless it’s just me?
No.. it’s for the reason indicated above.. I do not recommend the use of OTAs to pre-seed. I know it seems like the fastest way but I assure you that going through a new build (even if you have to wait for the review) is much more stable for users
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.