One of our users reported that searches are often timing out if the near me is included in the search query. While this can be avoided by excluding the near me part, and providing a proper location, there is a certain feature introduced by Google that shows the results for the near me searches, and it's not easily reproducible without that part.
On top of that, pretty much all searches are timing out if no location is provided, but some API calls with the location are also timing out. I'm not sure if this is because the feature is not implemented for that location, but in this case, we should probably return an empty successful search rather than an errored one.
One of our users reported that searches are often timing out if the
near me
is included in the search query. While this can be avoided by excluding thenear me
part, and providing a properlocation
, there is a certain feature introduced by Google that shows the results for thenear me
searches, and it's not easily reproducible without that part.On top of that, pretty much all searches are timing out if no
location
is provided, but some API calls with thelocation
are also timing out. I'm not sure if this is because the feature is not implemented for that location, but in this case, we should probably return an empty successful search rather than an errored one.Intercom