-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Place query hangs indefinitely on certain place_id #86
Comments
I tried a couple of them and they all return a value for the "err" arg in the callback function, showing they're invalid place IDs. Can you try using the latest commit on GitHub? |
I should have included that I was trying to catch the error
but the script was not returning -- anything :) this worked: "@google/maps": "git+https://github.com/googlemaps/google-maps-services-js.git", |
Cool, we should have a new release out soon. |
I am sorry to reopen this, I must be doing something wrong, because I am having the same problem today -- with the script not returning. After I re-installed with npm with
I did see an error with "status", and changed my err test to
and believe I process several place_id, but I am not sure how many. Now if I try the problem examples, this one for instance,
they hang. I tried reinstalling the package with npm again. Any ideas what I am doing wrong? |
+1 I am getting the same thing on certain IDs. Request just hangs indefinitely until (I think) the browser is timing out the request at 5 minutes. No matter the timeout settings etc. I use in the place request params it just hangs. For example a placeid of "foo" just hangs instead of sending back what I get when I do a request directly in browser which is "INVALID_REQUEST" |
For some strange reason, the following place_id hang silently and indefinitely for a place query. 32,000 succeeded fine. I don't know how to trap for the error. For me, it is consistently repeatable.
Using version 0.3.1 -- I didn't test an earlier release
using any of the following place_id
The text was updated successfully, but these errors were encountered: