Hi everyone!
For several days now I’ve been facing the problem of not being able to release new builds. OTA is not available for selection and new builds are simply not sent. At the same time, all records in the history are there, and updates are published to the web correctly.
Perhaps someone has encountered something like this?
@nick.carroll any ideas?
Hey @a.mutaliyev! I’ve been dealing with this issue since Monday.
It’s frustrating because this was the final step before launching my app, and my client is waiting.
I’ve submitted multiple tickets, but they keep saying they’re still working on it.
Do you have an existing app with the same bundle id in the app store? If you have an existing build from BDK for example, but the app was set to support both iphone and ipad, the build will not be sent because bubble mobile builds only explicitly support iphone devices. Unfortunately, Apple does not let you retroactively remove support for any devices.
While Bubble mobile apps can be downloaded on iPad, We don’t specifically support iPad yet because there is a lot more involved and it means Apple will test your app equally on both device types. This means it would be very possible for a user to shoot themselves in the foot, so to speak, by not being able to support ipad in a way that Apple requires.
If you do have an existing build that was marked as iphone + ipad when building the app with BDK, you will have to create a new app with a new bundle id. We will eventually support both, but it is lower priority compared to more foundational functionality.
If this is not the case, please lmk
I had an app published with Natively (so no iPad support)
I was able to generate builds and they were received by the Apple Store Connect without issue until last monday so I don’t think it’s related to this.
For me, the ipad app is more crucial than the iphone
Ah interesting, well thats better. What is your app id?
my app id is kowl
I also like @vella.mathis.pro have a wrapped app released to app store with Nativley. Also iPad support is disabled. But I knew about this problem long time ago, so I created a new app in appstore connect with a different bundle ID beforehand. Just then the builds published fine, but by trying to specify the bundle ID of an existing app, bubble was able to create a build, but couldn’t submit it to appstore connect, since apparently Natively builds do support iPad despite the toggle for that setting being disabled in their dashboard.
But as you could see from my screenshots, that’s not what we’re looking for at all. Since regardless of bundleID and having an existing iOS app, my mobile builds just stopped being created. That is, neither android nor iOS builds are created at all.
My app ID is recycle-app
Moreover in the history there are records of released updates which contain information that mobile builds as well as the web update have been sent, but I don’t get any errors, emails from bubble and nothing changes in the mobile section in settings
When was the last time you deployed? This will help me find the failed build in the pipeline
Last deploy was 11 feb at 13:31:17 (GMT +7)
Hmm not seeing a build from your app. Did you do a new build or OTA?
New build. As I said at the beginning of the thread and attached screenshots, when you publish an update there is no OTA available at all to choose from, and when you submit a new build nothing happens. I guess that’s why you can’t see the builds, they don’t exist 
And 3 developers have already faced the same problem.
Mind trying again?
Just did a new deploy for the web and new builds
Yeah thats super weird, its not hitting our deploy pipeline. There have been other successful builds so there is something deeper with your app. Will look into it asap
it’s the same with mine, I just tried again, and no build generated
I have the same issue with my app’s builds
@vella.mathis.pro @margaux.masson21 I just tried to send a new mobile builds and it worked fine for me so you can try it too
Why can’t you let us decide whether to push for iPhone or iPhone + iPad?
Let getting approval from Apple on iPad be our problem.
We plan on just using a webview for our V1 and basically using Bubble Native as a replacement wrapper for BDK, so I don’t see why we need to wait for you to optimize for iPad for us to push there.
If the app loads and shows the webview on iPad than we should be able to choose to push to it.
Am I missing something?
