Afraid not.
Because it’s a crucial part of the app in question have had to implement contigency measures until it is resolved - can’t sit on hands waiting. Though this is less than ideal as a lot of things are already “wired” up to the output of the search box so not a trivial amount of reworking needing to be done here.
Thanks @NoCodePhill . I’m in the same spot…not sure if I want to re-wire everything or wait for bubble to fix.
Hoping for transparency from bubble support.
Bubble support said they are handling this issue with “High” priority in escalation system.
I’m optimistic
Disappointed but glad others are here. I don’t remember when I first noticed it, at least a few days ago but I thought it was a temporary bug or that the device was not sharing the location properly, breaking the “Prefer results around” field.
This team has been great about addressing issues in the past and being transparent about what’s going on. I think our apps are in good hands.
Yes, this is a known issue that the bubble team says they are working to fix. Unfortunately, I haven’t been able to get an ETA on when it will be resolved and it is also crippling my app.
I have also faced this issue. After trying everything in Bubble and my Google Cloud Console such as reverting the last few days of new feature, creating new API keys, removing restrictions and creating new billing accounts, nothing has worked.
The issue I have is that my search box is not able to pull place names and their associated addresses like it has done in the past. The Geocoding API is shoing 4xx error but unable to give more details.
As a transportation booking system, this bug has made our bookings near impossible due to the hotel and accomodation names being invalid or not appearing.
Following this thread for updates
Are we 100% certain that the Bubble team is aware of this and that the AI is not lying to us? It told me it opened a ticket but I don’t see anything in my email about a ticket.
EDIT: Nm, I have a ticket, I see it on the support site. Says in progress.
Just to remind that you can still get results using something like Google Places plugin, and so can build your own workaround/solution. The issue lies with Bubble letting your keys take over on a custom domain, not with the API or your keys themselves.
Probably the route to take now I don’t think this has caused enough issues for enough people to make it high on the priority list.
If I comment on a post (and even when I don’t), you can be sure the team knows
Hey everyone, I’m being told this should be resolved now. Could you all check and let me know?
yes!!! amazing. thanks
Can confirm functionality has been restored on my end. 
Yes! Thank you!
