| Issue 9153: | Bug: android geocoder is not working | |
| 67 people starred this issue and may be notified of changes. | Back to list |
unable to fetch addressed through geocoder in android. 01-15 12:42:49.383 522-6664/? W/System.err: java.io.IOException: Timed out waiting for response from server 01-15 12:42:49.384 522-6664/? W/System.err: at android.location.Geocoder.getFromLocation(Geocoder.java:136) IMPORTANT: If you are seeing an incorrect location from the geocoder, please go to http://maps.google.com and enter your query there, and then select to "report an issue" to ensure it gets routed appropriately. Do not file the issue here. If you are seeing an unexpected response that only occurs when using the API and does not occur when using http://maps.google.com, then please include a link with your geocoding request, or to a webpage demonstrating the issue. ********************************************************* For developers viewing this issue: please click the 'star' icon to be notified of future changes, and to let us know how many of you are interested in seeing it resolved. *********************************************************
Jan 15, 2016
#1
[email protected]
Labels:
Internal-26576538
Jan 15, 2016
We are facing this same error since past 10 hours: W/System.err: java.io.IOException: Timed out waiting for response from server W/System.err: at android.location.Geocoder.getFromLocation(Geocoder.java:136)
Jan 15, 2016
First noted this issue around 15h00 GMT today.
Jan 15, 2016
Same here with cordova google map plugin.
Jan 15, 2016
Facing this error for last few hours in my newly built app, it was working fine yesterday
Jan 15, 2016
Till yesterday the whole thing was wrking nd suddenly its broken. stuck with this, nw had to chnge the logic to use web api Unable connect to Geocoder java.io.IOException: Timed out waiting for response from server at android.location.Geocoder.getFromLocation(Geocoder.java:136) at LocationAddress$1.run(LocationAddress.java:32)
Jan 15, 2016
i gave the same issue. i all the time get : "Timed out waiting for response from server" and i need to submit my project next week. i hope they will fix it.
Jan 15, 2016
have the same issue want to be alerted when it is addressed and working
Jan 15, 2016
Can confirm this. /sub for updates.
Jan 15, 2016
It seems to be working now. Check it.
Jan 15, 2016
Can we get an update on this? It's almost 12 hours since the service is not functioning.
Jan 15, 2016
i still have that issue.
Jan 15, 2016
Yes, this is unacceptable. This is effectively blocking our users from purchasing through our app. FYI to those following mapbox just released a drop in replacement for google's apparently unreliable geocoder:https://www.mapbox.com/blog/android-geocoder-library/
Jan 15, 2016
Hello, im still having this issue in my app, everything worked perfectly in last few days
Jan 15, 2016
I saw the service become intermittently responsive around 4am GMT 01/15/16. Then an apparent total service blackout until about 6pm GMT 01/15/16, and now it seems to intermittently responsive again.
Jan 15, 2016
Hong kong, Geocoder working now!
Jan 15, 2016
We're having the timeout issue as well. It's intermittent, but extremely high fail rate. And to make it worse, when geocoder.getFromLocation fails (after about 5 seconds), the app says it's unresponsive and suggests to the user to close it down. Our users are hitting this almost immediately after opening the app. (This is in spite of having getFromLocation on a bg thread, btw.)
Jan 15, 2016
working in India now
Jan 15, 2016
Also seems to be fixed in our app as well.
Jan 15, 2016
In Poland still not working.
Jan 15, 2016
In VietNam, it has not been working since yesterday, still not working now.
Jan 16, 2016
Any update on this? This is causing major issues in out app
Jan 16, 2016
#18 It should not give ANR if you are calling it from the background thread. Also I would recommend not to completely depend on the built in geocoder. Some devices doesn't come with the geocoder implementation, so you should rather use geocoder rest api to be safer. I hope you do check Geocoder.isPresent() before making any geocoding calls.
Jan 17, 2016
thanks for your reply, but did google resolved this issue that the built in gecodeing should not give a time out?
Jan 17, 2016
Nope, still not working for me.
Jan 17, 2016
any word from google on this somewhere?
Jan 17, 2016
We believe that this is now fixed. If you are still seeing issues, please clarify the approximate % of requests that are failing, and the name of the app, if you're willing to post that here. We will leave this ticket open for another day or so.
Jan 18, 2016
For me its still not working correctly, same problem..
Jan 18, 2016
(No comment was entered for this change.)
Status:
PendingFurtherReview
Jan 18, 2016
Okay, it started to work now.
Feb 9, 2016
(No comment was entered for this change.)
Status:
Fixed
Mar 31, 2016
Was working fine earlier but now only working on wifi, on Mobile network(2G/3G) gives timeout error
Apr 3, 2016
it is not working now with me here, it was working earlier today
Apr 3, 2016
Having same issue here even with WIFI
Apr 3, 2016
Not working for me today... (was yesterday)
Apr 3, 2016
Same here, not working for the last 4 hours (worked before)
Apr 3, 2016
stopped working this morning... getting the following error: "java.io.IOException: Timed out waiting for response from server at android.location.Geocoder.getFromLocation(Geocoder.java:136)"
Apr 3, 2016
same issue
Apr 3, 2016
Same problem since this morning ! This is very annoying, geocoder doesn't work in all situations ! Please fix it !
Apr 3, 2016
Not working for me too. In India it started in the evning April 3.
Apr 3, 2016
By it started..I mean the problem
Apr 4, 2016
Same problem since this morning !. stopped working this morning... getting the following error: "java.io.IOException: Timed out waiting for response from server at at com.google.android.gms.maps.internal.l$a$a.a(:com.google.android.gms.alldynamite:93)
Apr 4, 2016
Same problem I got .Yesterday its working fine today its not working "java.io.IOException: Timed out waiting for response from server
Apr 27, 2016
Same problem happening to me, Was working yesterday !
May 27, 2016
Timed out waiting for response from server ... in Hungary
May 27, 2016
Happens in USA also.
Jun 7, 2016
Hi, still having the same problem
Jun 8, 2016
Happens in Mexico too.
Jun 14, 2016
I see this issue on some Android devices only like Moto G running Android 5.1. Is there any work-around to avoid this?
Jul 11, 2016
I'm experiencing this issue now again, for my new app.
Jul 15, 2016
Strange that I am facing this issue in one of the two devices I tested. Also, it throws this exception only when I am on Mobile data, not on WIFI.
Jul 26, 2016
Using the following command: Geocoder geocoder = new Geocoder(context, Locale.getDefault()); I get the following error message: Unable to connect to Geocoder java.io.IOException: Timed out waiting for response from server android.location.Geocoder.getFromLocationName It use to work. I didn't make any change in the code. and it stop working
Aug 2, 2016
When I tried to get the address using the Google map to pass the Lat and Lang The Most of the time I am getting this following issues. java.io.IOException: Timed out waiting for response from server android.location.Geocoder.getFromLocation(Geocoder.java:136)
Aug 3, 2016
Not working for me: java.io.IOException: Timed out waiting for response from server at android.location.Geocoder.getFromLocation(Geocoder.java:136) at com.app.MapsActivity$Section.prepareRoute(MapsActivity.java:1582)
Aug 31, 2016
We can confirm the reports coincided with Maps backend issues. Those are fixed now and monitoring was put into place to ensure we are able to address such problems quicker in the future. As for your code/applications - please consider implementing an exponential backoff when encountering failures, this will ensure your apps can handle service interruptions gracefully.
Status:
Fixed
Sep 3, 2016
It does not seem to be fixed for me, my app still returns:
java.io.IOException: Timed out waiting for response from server
at android.location.Geocoder.getFromLocation(Geocoder.java:136)
at com.eazybike.MapsActivity$Section.prepareRoute(MapsActivity.java:1546)
at com.eazybike.MapsActivity$Section$5.onLocationResult(MapsActivity.java:1503)
at com.google.android.gms.location.internal.zzk$zza$1.handleMessage(Unknown Source)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6077)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
Sep 6, 2016
Thanks for reporting the issue again edumucelli! Are you still experiencing it?
Status:
Accepted
Sep 6, 2016
Yes, same error still to this date on a Nexus 5X running Android 7, and play services-related packages version 9.4.0. In detail, some info from my gradle: compileSdkVersion 23 buildToolsVersion '23.0.2' compile 'com.google.android.gms:play-services-maps:9.4.0' compile 'com.google.android.gms:play-services-location:9.4.0' compile 'com.google.android.gms:play-services-places:9.4.0' If you want, I can send a more detailed report a. Just let me know what to collect. For now, I have just switched to the Maps Geocoder API, handling all the JSON with Gson/Volley.
Sep 14, 2016
Hi again edumucelli, We've been investigating the issue on our side, and found a few latency spikes that affected the Android geocoding service over the last few days. However, the spikes appeared to be quite short-lived each time they occurred, so our users should to our current best understanding not have suffered from any long-lasting geocoding failures. We have now addressed the underlying issue in our backends that caused the spikes, but it would be good to know if you still see the issue. Also, have the errors been sporadic or systematic, and if the latter, would you be able to within the hour when the issue started and how long did they last? If you experience occasional geocoding call timeouts and the functionality of your application depends on a successful geocoding call, having retry logic would improve reliability. Using an exponential backoff when retrying is generally good practice, preferably with a component of random jitter added. Adding a bit of random jitter is actually good practice when doing any calls, not just retries. Anyhow, we also continue investigating ways to make the Android platform geocoder user experience more robust for our users, and to smooth the latency spikes they might experience.
Sep 16, 2016
I got the issue - Timed out waiting for response from server - like below; I tested the code in the following devices; 1. Moto-e running on Lollipop 2. Swipe Marathon running on Kitcat 3. iBall slide running on GingerBread 4. Moto-g running on Marshmallow I used the following code; A. using the Geocoder class with getFromLocation() B. using the AsyncHttpClient to the URL - http://maps.googleapis.com/maps/api/geocode/json? Option A; works on devices 1 and 4 perfectly not working on 2 and 3 devices Option B; works on 1 and 4 sometime not works on 2 and 3 Hope this may help! Please rectify asap.
Oct 3, 2016
i also face the same issue since morning
Oct 13, 2016
We are experiencing the same problem this morning, affecting all devices we have tested (Android 5-6).
Oct 17, 2016
facing the same problem java.io.IOException: Timed out waiting for response from server
Oct 18, 2016
Facing this issue occasionally: java.io.IOException: Timed out waiting for response from server
Oct 21, 2016
i also face the same problem since this morning
Oct 21, 2016
Unable connect to Geocoder java.io.IOException: Timed out waiting for response from server at android.location.Geocoder.getFromLocation(Geocoder.java:136) Facing this from morning.plz solve this issue becoz tomarrow we have issue production
Oct 21, 2016
it's working properly now
Oct 21, 2016
its working now
Oct 27, 2016
Issue 6745 has been merged into this issue.
Oct 31, 2016
Issue 9549 has been merged into this issue.
Nov 1, 2016
Issue 10613 has been merged into this issue.
Nov 4, 2016
Still have
11-04 11:43:59.306 15232-15764/? E/AddressIntentService: Network or other problem
java.io.IOException: Timed out waiting for response from server
at android.location.Geocoder.getFromLocation(Geocoder.java:136)
at com.xyz.xyz.geo.AddressIntentService.onHandleIntent(AddressIntentService.java:55)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Works on my Nexus5(6.0.1) but not on my NexusP6 (7.1.1). Using MapBox as a fallback. Please fix this.
Nov 7, 2016
Still not working... "java.io.IOException: Timed out waiting for response from server" from last night on MOTO G3(6.0.1).
Nov 8, 2016
(No comment was entered for this change.)
Labels:
-ApiType-Geocoder ApiType-Android2
Nov 9, 2016
(No comment was entered for this change.)
Labels:
-ApiType-Android2 ApiType-AndroidPlaces
Nov 13, 2016
still not working!!!!
Nov 30, 2016
Unable connect to Geocoder
i am using sony and android version5.1.1
E/FetchAddressIS: Sorry, the service is not available
java.io.IOException: Timed out waiting for response from server
at android.location.Geocoder.getFromLocation(Geocoder.java:136)
at com.sample.sishin.maplocation.FetchAddressIntentService.onHandleIntent(FetchAddressIntentService.java:95)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:211)
at android.os.HandlerThread.run(HandlerThread.java:61)
Nov 30, 2016
Hi good
Dec 19, 2016
Every time when on 3G/LTE, Geocoder.getFromLocation() fails: java.io.IOException: Timed out waiting for response from server Time out is happening only on mobile connection. when on WiFi, works without every time.
Dec 27, 2016
it's really frustrating to receive this stupid error
Jan 27, 2017
I receive the timeout on my Nexus 6P with Android 7.1 but not on a Samsung with Android 5.1 nor Moto G2 with Android 6. I've been experiencing it for at least yesterday. Every device is on WiFi I've been reproducing it on Nexus 6P for hours now |
|
| ► Sign in to add a comment |