Google会将现有自动填充参考的详细API调用返回NOT_FOUND [英] Google places details API call return NOT_FOUND for an existing autocomplete reference

问题描述

我有个问题，也许有人遇到了同样的问题。

我打电话给google地方autocomplete api call。

然后，我向用户介绍结果，他可以选择该地点。
根据我选择的地点详细信息调用并检索该地点的详细信息。

我的问题是某些情况下，细节服务返回NOT_FOUND。完整的响应看起来像这样

  {\ n \debug_info \：[]，\\\
 \\ \\html_attributions \：[]，\\\
 \status \
：\NOT_FOUND \\\\
} \ 
  

基于google api文档，NOT_FOUND表示详细信息：
NOT_FOUND表示在Places数据库中找不到引用的位置。

但是我在1秒前从自动完成服务调用中获得了此引用！

任何人都有同样的问题？ p>

感谢，
Noam

解决方案

，一个用于自动填充建议，另一个用于地图细节。您会看到两个索引在不同时间更新的结果。如果您提供的是有问题的地址，我可以向相应的团队确认，或者您可以等待几天后索引重新同步。

I have a problem maybe someone had the same issue.

I am calling google places autocomplete api call.

Then i am presenting the user with the results and he can select the place. Base on the selection i am making places details call and retrieve the details of the place.

My problem is that some cases the details service return NOT_FOUND. the full response looks something like this

    {\n   \"debug_info\" : [],\n   \"html_attributions\" : [],\n   \"status\" 
: \"NOT_FOUND\"\n}\n

Based on google api documentation, NOT_FOUND for place details is: NOT_FOUND indicates that the referenced location was not found in the Places database.

But i got this Reference just 1 sec ago from autocomplete service call!

Anyone has the same problem?

Thanks, Noam

解决方案

There are two indexes here, one for the autocomplete suggest and one for the map details. You are seeing the results of the two indexes being updated at different times. If you supply the address in question, I can confirm with the appropriate teams, or you can just wait a couple of days for the indexes to come back into sync.

这篇关于Google会将现有自动填充参考的详细API调用返回NOT_FOUND的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！