I’m trying to publish an update for my app (ubud v0.10.0) to an existing App Store listing that was originally created using BDK Native, but I keep running into build errors when exporting via the new Bubble native mobile build tool.
Both my Apple and Android builds failed with the following errors:
• Apple error code: Unknown error 1747786462872x387532390826118140
• Android error code: Unknown error 1747786916501x537166999264323100
I’m logged in to the correct Bubble account and followed the normal build process. Has anyone successfully published a build to an existing App Store listing using the new Bubble native export (not via BDK)? Or do I need to create a new listing entirely? It would be really helpful to keep the same listing, particularly as Google requires 14 days of testing for a new app.
Appreciate any guidance or experiences from others who’ve gone through this.
Indeed, currently, bubble and its docs are not thought for already published mobile apps.
It all starts with the build number. If your app is already published with version 4.0.0 for example, the stores need you to upload a build that has a higher version than that.
Currently, bubble doesn’t let you manually override the version number and you need to start with version 1.0.0 maximum.
The solution is to just create builds 1.0.0, 2.0.0, 3.0.0, 4.0.0. They are all going to fail, and after that, you can create a build with a higher version that is going to work.
Important notes for Android
It is normal that your initial build fails to upload. The first time, you need to upload your build manually in the play console.
Keystore : do not follow bubble docs. You need to use the keystore that was initially used to sign your app
Hope this helps 
1 Like
Keystore : do not follow bubble docs. You need to use the keystore that was initially used to sign your app
What part of the bubble docs for android should be ignored?
Thanks - this is really helpful.
I’ve followed your advice but unfortunately still getting ‘Unexpected error’ when I publish the build
@nick.carroll Could someone in your team take a look? I put a ticket in 4 days ago but haven’t back…
If you already have an app published in Google play, you should be using the keystore that was used to initially sign the app, and not create a new one.
Using a new keystore is possible though, but you then need to request a keystore file change by Google and this takes a couple of days from what I know.
Ahh I did not know about the need to request a keystore file change from Google, thanks for flagging. Will look more into it & update the docs
