Native Searchbox Geographic Places Results No Longer Accurate

ncat · 2024-09-05T19:06:42.074Z

Hello,
I have noticed that the native searchbox geographic places search functionality seems to have changed. Before it would display exact addresses, but now for the most part is is suggestions locations that are “near” to what you typed in and the search results do not seem to be accurate for the most part anymore.

One example is if I type in “LAX A”, the correct result comes up. However, if I type “LAX Airport” No search results appear.

Is there a setting that I am missing to fix this or did Bubble change something? Thank you!

image782×149 8.84 KB

image727×416 82.8 KB

ctingle · 2024-09-06T00:18:00.241Z

I’m having the same issue…Autocomplete on a geographic places search randomly stopped working two days ago. I checked all Google API keys and credentials and did not see any issues or notifications.

ncat · 2024-09-06T00:20:36.346Z

Hi @ctingle,

Thank you for also confirming. I am glad that I am not the only one experiencing this. I submitted a bug report documenting this, so hopefully this is expedited.

ncat · 2024-09-06T00:54:11.630Z

I received an update from Bubble regarding this behavior:

“Our engineers are currently aware of this behavior and are working to determine a fix as soon as possible. In the meantime, I have forwarded your information over to our team. I’ll be sure to update you on any new information as it comes in.”

I will post here again and close out this thread once it is resolved.

german · 2024-09-06T02:48:15.482Z

I can confirm I noticed this 2 days ago. Glad to hear Bubble is working on it. Please report any updates. Happy to report myself if it helps streamline resolution.

ncat · 2024-09-06T05:28:36.154Z

Thanks @german

Yes, I think it would be beneficial if you could file a bug report with what you are experiencing as well so they have more data to work through the issue.

german · 2024-09-06T13:58:42.989Z

Will do

ctingle · 2024-09-06T23:03:06.332Z

I’ll submit a bug report as well.

ncat · 2024-09-07T18:13:52.190Z

Update: I asked for an ETA on when we could expect this bug to be fixed and this is the response that I received.

“While we don’t have an ETA at the moment, please rest assured that we’ll keep you updated with any new information as soon as it becomes available. We know how crucial this issue is, and our team is working hard to resolve it as quickly as possible.”

While I I understand that they can’t provide an exact ETA, its a bit frustrating that they couldn’t answer if this would be fixed in a few days or a if this would take weeks to resolve. I am still hoping for the best though and do have faith in the bubble team that this will be resolved sooner rather than later.

thibautranger · 2024-09-09T10:04:41.997Z

Same issue here

Glad to know they are working on it, but this bug has been here for almost a week now, kind of disappointed by the time this takes to be fixed as it is such an important feature for thousands of apps !

ncat · 2024-09-09T20:47:21.280Z

Agreed! At this point I am extremely disappointed by the lack of transparency here. From the correspondence I had with the but bug reporting team I thought this would be fixed within a day or two. Now, I have no idea when it will be fixed since they refuse to give an ETA. This is affecting so many people. I have been getting really concerned about reliability lately and this is not helping ease my nerves…

ncat · 2024-09-09T21:13:27.565Z

Actually, I just heard that this may have been fixed today. I will check and followup here as well.

ncat · 2024-09-10T13:28:36.100Z

Bubble support has confirmed that this bug has been fixed.

system · 2024-11-14T19:07:14.095Z

This topic was automatically closed after 70 days. New replies are no longer allowed.