Can’t connect Bubble to Google Play — “Package name not found in your Google Play Developer account

Mobile Beta
1

I’m trying to publish my Bubble app to the Google Play Store and got stuck in a loop.

  • I generated a keystore successfully.

  • When I go to Settings → Android Play Store, Bubble asks for:

    • Package name

    • JSON key

    • Keystore info

  • No matter what I enter, I get:
    “The package name was not found in your Google Play Developer account.”

  • The problem is, I can’t build the AAB without first connecting Bubble to Google Play, but Google Play won’t recognize the package name until an AAB is uploaded — a catch-22.

  • I tried package names like com.redesignedby.rdby and com.ruby.final.

  • My Google Cloud service account is connected in Play Console under API Access, and I’m using that JSON key in Bubble.

  • I suspect it might be an API permission or validation issue.

Question:
How can I generate and upload an AAB when Bubble blocks me at the “Validate Android Settings” step

Screenshot 2025-11-11 at 21.59.46
Screenshot 2025-11-11 at 21.59.46838×928 82 KB

? Is there a workaround or correct sequence to register the package name before connecting?

2

This is a new thing that was only released the last few days, maybe @fede.bubble can help? I did this a few weeks ago and you are correct, the first google play release needs to be manually uploaded.

Did you set up the service account?

3

I’ve done all the steps. checked them several times.

4

Everyone is telling me to find the package namer in Play console. but there is no where to find it.

I’ve created an app but theres no package name, to set up or find

5

Had the exact same issue today and bubble support had no idea what I was talking about. You need to first deploy your app and get the build package. Then upload it into the play console under a new test release (watch bubble tutorial). Then come back and click connect.

P.S. my app failed the first time but worked the second time

6

Ok. So even though it’s not “connected” I will get the Android files I need since i’ve posted all the other stuff?

I guess it’s just confusing UX. I thought I could not get the file if the Connection was not done.It’s unintuitive. Thank you sir!

7

We’ll be addressing this confusing UX immediately, apologies for the confusion

8

I mean, it makes sense now after the fact. It’s just that in the video tutorial he just puts something as package name! :stuck_out_tongue:

Thanks bro!

9

Ok we have updated the validation step to not check the package name on initial connection. The package name will still be used in subsequent builds to make sure the build is uploaded to the Google Play store properly, but the first build still needs to be uploaded manually to the Google Play console per their instructions.

11

i still can’t connect or deploy. it just says to validate google play store settings. but i can’t because of the package name. i’ve been trying to figure this out for days. it’s pretty frustating paying so much for this and it doesn’t even work….. and then i find out most of the posts here were from 10 years ago…. jeez what are you still selling this for?

12

I am facing the same issue I have an open ticket #51083704 you may refer to the chat correspondence.

For a brief period of around 12h I was able to connect to Playstore with no valid package name and no .aab Download email.

I was then advised by Specialised Team to reset my mobile app package name due to a potential conflict with prior attempts and voila…

The same validation check returns and fails, even if I regenerated a whole new JSON key and keystore with new identifiers.

Buried in Bubble documentation there is mention of an Appfile, over which I seem to have no control over to input my desired package name.

image
image945×149 7.21 KB

It seems like there is manual intervention to have enabled my first connection using this in the backend, but upon resetting, the default package validation checks returned.

13

Is this the first time trying to connect to the Google Play Store or had you previously kicked off builds from Bubble? If its the first time trying to connect, the validation step should not be checking the package name (because it doesn’t exist yet)

14

Also having the same issue here. When I first pressed connect. I received a success message and it said “connected” next to the Android Play Store label in the settings. When I clicked Deploy I had the option to deploy but I decided I wanted to change the package name. I went and changed package name and then the “Package Name not Found” alert showed. I changed it back to the original package name that was successful and the same alert came. I am now unable to Deploy and it’s asking me to upgrade my plan eventhough I’m on mobile starter plan. Any fixes for this yet?