Apple has recently updated their developer terms and conditions. Builds will fail if you haven't accepted the new terms at developer.apple.com. If your iOS builds were working and the latest one is failing, this could be a culprit!
Deploying to an Existing Bundle on the App Store with iPad Support
If you are trying to deploy to an existing bundle on the App Store that was previously published, you may encounter a Validation failed (409) error. This can happen when the bundle was originally published with explicit support for iPads, either from a wrapped Bubble web app or independently.
It's important to note that Bubble Native Mobile does not currently support iPad apps. If your app was originally a wrapped Bubble app that explicitly supported both iPhone and iPad before building the native mobile app, this could be the reason for the error you are experiencing.
Apple has strict guidelines when it comes to removing support for devices once a version has been published to the App Store. This means that if your app was previously published with iPad support, you cannot remove it and expect the build to be approved by Apple. The only solution in this case is to create a new app with a new bundle ID.
First Android Build
Congratulations on building your first Android app! If this is your first time doing so, you may encounter an error message. The error message you may receive is:
If this is your first time deploying your Android app to the Google Play Console, you will need to manually upload the aab file you received in your email. This is only required the first time you deploy to the store.
In order to successfully publish your app on the Google Play Store, you will need to manually upload the .aab file that you received in your email. This file is required by Google Play and will be the one you upload to your developer console.
Please note that this manual upload is only required for your first deployment to the store. For all future updates, you can simply use the Google Play Console to publish your app.
Before deploying, ensure that critical pre-deployment steps are complete: upload a valid keystore file, configure the package name correctly (e.g., com.yourcompany.appname), set up Firebase for push notifications (if required), and verify that your app display name and icon meet Android guidelines.
For missing Android build files where only iOS ones are received, ensure your app's "Deploy track" is set to Internal and "Release status" is set to Draft. Also, confirm that a valid .keystore file is uploaded in the Bubble settings, followed by retrying the build.
Neither PUB key nor PRIV key
If the error persists, verify that the JSON key format adheres to Bubble's compatibility requirements. If necessary, regenerate the JSON key through Bubble’s help guide and upload it anew.
If you receive the error message, Neither PUB key nor PRIV key, this has previously indicated issues with the JSON key uploaded to the app's Android settings:
To resolve this, we'd recommend these steps:
following these instructions to generate a new JSON key
upload this key to your Mobile settings
attempt a new build
To further investigate keystore-related issues, verify that the keystore alias and associated password are correct. You can also validate the keystore by running the command:
keytool -list -keystore my-upload-key.keystore
If validation fails, recreate the keystore and update your settings in Bubble.
Google API Error: Caller Does not have Permission
Additionally, if you encounter the error PERMISSION_DENIED, make sure your Google Play Android Developer API is enabled. Visit the Google Play API Console, enable the service for your project, and allow some time for the changes to take effect before retrying.
If you receive the error message, Google Api Error: Invalid request - The caller does not have permission, that usually indicates that you have the Release status Android setting selected to a Release status that isn’t Draft:
All other options do not work at this point. Engineering is planning on removing this option moving forward, but you should pick the Draft option in the meantime.
If you continue to have issues with your mobile app build after following these troubleshooting steps, please contact our Support team through the AI bot. You can express that you'd like to report a bug or talk to a person.