Yesterday we took an app to a custom domain and went live. It required we use Google Map API’s geolocation services even though we don’t use a map feature. In order to go live, we set up our own Google Keys.
In reading the forums, I came across this post (Why are Google API keys required? - #4 by keith) and a comment from @sudsy stating that if you use a geographic address in your db - whether you actually use it or not - Bubble loves it some API keys. Fine, all good.
However, with the app being live for merely a few hours, I got an email from Bubble:
“We are sending this email to let you know that your application Family Member Care is being rate-limited because of a high number of Google Map loads. This means that some users will be unable to see the map elements on your pages.”
Anyone experienced this? I’m about to reach out to support, but figured I’d check here too…
Cheers,
Ben
P.S. Also, we’ve only actually gone live with the landing page, so it’s not about actual ‘user’ use in any case.
You need to configure your own Google Maps account and API keys.
(You misunderstand my message you referenced: I’m talking about an open access demo app that anyone can inspect. Of course I could never put my own API keys there. You, on the other hand, have need for your own maps/geocode keys. Time to do that.)
Have you made that change live? You can look in the Network tab of dev tools to see what API key it is using when calling maps.googleapis.com/maps/api/js.
In the header for calls to that API, you’ll see your key. If it doesn’t match your own key, an you’re sure you have it configured properly in your Bubble app then contact Bubble support via their bug report form. Here’s how to find what key your app is using in production:
From a quick check of a free app without a key, it looks like the default Bubble key is:
AIzaSyDrc7Z2Xh0LNmHty4bO9Jine0mnKpx6p9Q
If that’s what you see for the value of the key query parameter, then your app is using Bubble’s key and not your own key. I have seen this happen before with one of my own apps and did report a bug about it a long-long time ago, so it’s possible. (Said bug was resolved a long-long time ago, but reversions happen.)
And, BTW, even if you’re not embedding a Google map, note that the Bubble geographic address datatype is a live connection to the Google geolocation API. The User data type has a “current location” field on it that is a geographic address, which would seem to be at least one reason why one’s own key is required, among others.
Alas, on my live page I don’t even have that API call.
And when I double-check in my app for the keys, I’m not using the default one you list for either Geocode API or Maps API (which are the ones I copied from my google dev credentials).
Adding this for peeps that might get the same thing. I heard from support: In short, if your domain gets visited but you’ve not gone Live yet (which shows a Bubble template) , it’s NOT using your Google API keys, even if you have added your own.
From support:
"This email can be sent if your Live domain was visited without you deploying to Live. When you haven’t deployed the app to Live yet, the Bubble boilerplate template shows. This template uses Google APIs. If you haven’t deployed to Live yet, your Google API keys are not yet used in Live so this can explain this email. This is the template for your reference:
This boilerplate template uses Google Maps so if you haven’t deployed to Live yet, but have added your keys in Development, your keys are not being used when the Live site is hit."
