IssueTracker

Hi,

I have the exact same issue. It was always working fine but it has stopped working in all my 4.1.1 devices.

What's going on?

Thanks.

This is annoying. An upgrade to 4.1.1 causes Geocoder.getFromLocationName to throw "IOException: Service is not available"

For others in the same situation, I have been using a fallback implementation of getFromLocationName to get an Address from a location name. I have attached the implementation; it is an async task and requires synchronization between the thread performing the geocoding and the async task (e.g. via wait-notify).

Arun

Regarding Comment 2, note that I have implemented a small subset of the Address interface that suited my needs. The json response may be parsed further to support more.

Arun

According comment #2 - thanks for the workaround.
But write an own Geocoder class is not so good solution as for me.
I hope that the regression will be fixed in nearby release.  

The issue isn't reproducible in v4.1.2!

Just after having received v4.1.2 it worked fine, but now it's buggy again.

I have the same problem on my SamsungGalaxy SIII 4G which runs on 4.1.1.  (Exception Error message is "Service not Available", and Geocoder's isPresent function returns true)  Unfortunately my phone says all updates have been installed so I can't do much about it as yet.

I can reproduce the bug in v4.1.2 Build number: JZ054K, Galaxy Nexus.

I have seen this issue occur on Multiple phones running 4.0.3, 4.0.4, and 4.1.1. Is this a service issue or an OS issue?

My Samsung Galaxy SII with Android 4.0.4 throws this exception TODAY. It never happened until now.
No problems found on emulators (APIS 8, 10, 15, 16) or on a Motorola Defy (running Froyo).

We are seeing the same problem on all our 4.0.x and 4.1/4.2 devices.  This started on December 3rd with the deprecation of the Google Maps Android v1 API (https://developers.google.com/maps/documentation/android/v1/).  This would seem to be a service issue.

[Comment deleted]

This is only solution for this problem....

public static JSONObject getLocationInfo(String address) {

                HttpGet httpGet = new HttpGet("http://maps.google.com/maps/api/geocode/json?address=" +address+"&ka&sensor=false");
                HttpClient client = new DefaultHttpClient();
                HttpResponse response;
                StringBuilder stringBuilder = new StringBuilder();

                try {
                        response = client.execute(httpGet);
                        HttpEntity entity = response.getEntity();
                        InputStream stream = entity.getContent();
                        int b;
                        while ((b = stream.read()) != -1) {
                                stringBuilder.append((char) b);
                        }
                } catch (ClientProtocolException e) {
                } catch (IOException e) {
                }

                JSONObject jsonObject = new JSONObject();
                try {
                        jsonObject = new JSONObject(stringBuilder.toString());
                } catch (JSONException e) {
                        // TODO Auto-generated catch block
                        e.printStackTrace();
                }

                return jsonObject;
        }
       
        public static GeoPoint getGeoPoint(JSONObject jsonObject) {

                Double lon = new Double(0);
                Double lat = new Double(0);

                try {

                        lon = ((JSONArray)jsonObject.get("results")).getJSONObject(0)
                                .getJSONObject("geometry").getJSONObject("location")
                                .getDouble("lng");

                        lat = ((JSONArray)jsonObject.get("results")).getJSONObject(0)
                                .getJSONObject("geometry").getJSONObject("location")
                                .getDouble("lat");

                } catch (JSONException e) {
                        // TODO Auto-generated catch block
                        e.printStackTrace();
                }

                return new GeoPoint((int) (lat * 1E6), (int) (lon * 1E6));

        }


GeoPoint srcGeoPoint =getGeoPoint(getLocationInfo(fromAddress.replace("\n"," ").replace(" ", "%20")));
                        GeoPoint destGeoPoint =getGeoPoint(getLocationInfo(CalDescription.toAddress.replace("\n"," ").replace(" ", "%20")));

We were able to correct this problem by simply rebooting our devices.  It now works on all 4.x+ devices.

i have the same problem  in  Nexus S 4.1.2 with rebooting works fine thanks

Galaxy SII 4.0.4 working properly after rebooting. Thanks.

Same happened on all my test devices. This is a terrible bug! I'm guessing it's the Google Play Services update that has been silently rolled out.   Google, you must do something to fix this without a device restart! Our apps will appear totally broken without it!

I had the same problem with a GalaxyNexus. It was fixed after a reboot

Rebooting on Galaxy Tab 10.1V solved the problem

solved after rebooting on android 4.1.1 galaxy note2

The same for Galaxy SIII with 4.1.2. Reboot solved the problem

I have the same problem in HTC One V version 4.0.3. And it happens again and again (don't know how long exactly). Reboot fixed and then after few days it comes back again. I cannot get any location update when this thing happens. My App based on this, I cannot ask our users restart their phones. Can anyone tell me the reason and how to solve it without restart the phone.

Same problem on Galaxy Tab 10.1 after updating to Play services

i have the same problem now.but after restarting my device it still shows the same issue

03-01 11:34:36.580: W/System.err(7163): java.io.IOException: Service not Available
03-01 11:34:36.580: W/System.err(7163):         at android.location.Geocoder.getFromLocation(Geocoder.java:136)
03-01 11:34:36.595: W/System.err(7163):         at in.wptrafficanalyzer.locationreversegeocoding.MainActivity$ReverseGeocodingTask.doInBackground(MainActivity.java:154)
03-01 11:34:36.600: W/System.err(7163):         at in.wptrafficanalyzer.locationreversegeocoding.MainActivity$ReverseGeocodingTask.doInBackground(MainActivity.java:1)
03-01 11:34:36.610: W/System.err(7163):         at android.os.AsyncTask$2.call(AsyncTask.java:264)
03-01 11:34:36.610: W/System.err(7163):         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
03-01 11:34:36.610: W/System.err(7163):         at java.util.concurrent.FutureTask.run(FutureTask.java:137)
03-01 11:34:36.615: W/System.err(7163):         at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:208)
03-01 11:34:36.615: W/System.err(7163):         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
03-01 11:34:36.625: W/System.err(7163):         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
03-01 11:34:36.625: W/System.err(7163):         at java.lang.Thread.run(Thread.java:856)
 
give me a solution

i just got a solution ,try this.

# Project target
target=Google Inc.:Google APIs:16

The reason is that the Geocoder class is present in the core Android framework, but depends on code contributed by the Google APIs to function properly. Even if your AVD includes the Google APIs, your project still needs to be built against that specific build target.

http://stackoverflow.com/questions/15129900/reverse-geocoding-stops-works-in-android-map-version-v1/15152089#15152089

Tested with 5 devices, on two it worked, three had the bug.
On two of them it was gone after a single reboot, another needed to be rebooted twice before it worked again.
The bug appeared even with Google APIs targeted (comment #25).

Geocoder reliability definitely needs to be improved.

Maybe this is related to the recent update of Google Play services.

Same problem. This all started the exact time google updated their play store. Happening about once a week. All my users must reboot their devices in order to geocode.  It there any fixes or updates coming up anyone has heard? Thanks in advance.

In looking at the thread on stack overflow, I don't see changing the project build target to 16 as being accepted as the answer to the problem by the original poster.  Do you have some more detail on this position?  I'll add a comment there as well, asking for clarification.  

It would seem to me, the best solution is having your own code to handle the call to the geocoder service, at least as a fallback.  I've not tried as yet but there are a couple examples above that seem promising.  

There' a new Play Services, does that help?

My observations:
1) It's not reproduced with android 4.2.x (device) + target API 17 (app)
2) Probably it's not reproducible in android 4.1.x + target API 16.
3) Probably it's periodically reproducible in android 4.0.x + target API x
4) It's not reproducible with android 2.x.x
Please share your observations with android version plus target API.

To #29: It does not help.

I suspect that this is a rate-limiting issue. Can anybody confirm or refute that it only happens when the API is used a lot?

Same issue[java.io.IOException: Service not Available]. Trying to find solution to close this bug. No luck still now. This doesn't happen all time whenever i am accessing the geocoder but it occurs only sometime, its really unpredictable.

Could anyone share their views on this ?

Same here. I made an app using the Geocoder that worked fine yesterday evening and then started throwing the exception this morning for no apparent reason. A restart fixed it for now; who knows when it'll start acting up again.

To #13: I'm sorry, your solution does not help.
Occurs on S3, 4.1.1.

Same problem, reboot fixed it.
In addition, I have spent some hours because LocationListener methods was never called after the LocationManager.requestLocationUpdates() call.
Rebooting "fix" this problem too.

Same problem on Samsung Galaxy SII (GT-I9100 - Android 4.1.2) and Samsung Galaxy S3 Mini (GT-I8190 - Android 4.1.2)

05-13 20:51:34.573 W/System.err( 4468): java.io.IOException: Service not Available
05-13 20:51:34.573 W/System.err( 4468):         at android.location.Geocoder.getFromLocationName(Geocoder.java:178)

After Reboot my SGS II the problem is solved, but what  can I say my customer with the other device? Reboot your device please?

Does this affect 4.2.2?

I saw this issue again today on my Galaxy S2 ICS. My app could not get address but Google Map application (genuine one) shows address normally. Why can it work? Is it calling different API or using different service? After seeing Google Map works fine, my app still failed to work.

How do I recover this? Reboot. That is the only one way I know for this issue.

Many new features are introduced in Google I/O 2013. They are fine and we need them to make things better. But please take a moment to fix critical issues too.
 

[Comment deleted]

Same problem, reboot fixed it too.
In same cases, locationManager.getLastKnowLocation() works, but it can be out-of-date....
We can't ask our user to reboot their devices, and we can't use out-of-date locations... Please give us a solution

I got this error in Galaxy Tab2 when reverse geocoding. It occurs weekly once.Then restart my device reverse geocode done properly.
Is it any work around to fix this issue.
Shall we restart google services while this exception caught?

Is there any workaround for this? Can we rely on GeoCoder , or need to use the solution as in #13!

#2, it works

This report applies to a mobile Google application or service, and the issue tracker where you reported it specializes in issues within the Open Source source code of the Android platform.

We are not able to provide support for Google products in this issue tracker. Please use the Google Support site for help at https://support.google.com/ or report this issue in the most appropriate Google Product Forum at https://productforums.google.com/forum/#!forum/en/ and especially in https://productforums.google.com/forum/#!forum/mobile

For Maps API issues, see https://code.google.com/p/gmaps-api-issues/

 #25 Sorry,your solution didnt help me..

I dont know what happens, but today magicaly it works. I udpdate the sdk but the maps in my proyect didnt work, then i created a new proyect, copy-paste from my old proyect, acquired a new key from google maps v2, loaded the new maps library, run and the maps and Geocoder works. Tested in a Samsung SIII mini. Sorry for my english

#49 Probably you have got an update Android 4.2.2 Jelly Bean on your Samsung SIII mini.
It's periodically reproducible on: 4.0X, 4.1X
And it's not reproducible on 2.X, 4.2X

Currently I am using a hybrid:
try {native Geocoder}}
catch (IOException) { http request (see #13)}

Note: There is a limit: 2500 request per day for http requests
If you continue to exceed this limit, your access to the Geocoding API may be blocked.
https://developers.google.com/maps/documentation/geocoding/#Limits 

Mmmm i realize that the service only works with some mobile operators. With Movistar works fine, with Claro or Tigo doesnt work.I dont know why. The service of the app Heywire also only works in Movistar.

Hi all, this is my workaround solution for the reverse geocode (hope to help someone):

        public static List<Address> getFromLocation(double lat, double lng, int maxResult){
               
                String address = String.format(Locale.ENGLISH,"http://maps.googleapis.com/maps/api/geocode/json?latlng=%1$f,%2$f&sensor=true&language="+Locale.getDefault().getCountry(), lat, lng);
                HttpGet httpGet = new HttpGet(address);
                HttpClient client = new DefaultHttpClient();
                HttpResponse response;
                StringBuilder stringBuilder = new StringBuilder();

                List<Address> retList = null;
               
                try {
                        response = client.execute(httpGet);
                        HttpEntity entity = response.getEntity();
                        InputStream stream = entity.getContent();
                        int b;
                        while ((b = stream.read()) != -1) {
                                stringBuilder.append((char) b);
                        }
                       
                        JSONObject jsonObject = new JSONObject();
                        jsonObject = new JSONObject(stringBuilder.toString());
                       
                       
                        retList = new ArrayList<Address>();
                       
                       
                        if("OK".equalsIgnoreCase(jsonObject.getString("status"))){
                                JSONArray results = jsonObject.getJSONArray("results");
                                for (int i=0;i<results.length();i++ ) {
                                        JSONObject result = results.getJSONObject(i);
                                        String indiStr = result.getString("formatted_address");
                                        Address addr = new Address(Locale.ITALY);
                                        addr.setAddressLine(0, indiStr);
                                        retList.add(addr);
                                }
                        }
                       
                       
                } catch (ClientProtocolException e) {
                        Log.e(MyGeocoder.class.getName(), "Error calling Google geocode webservice.", e);
                } catch (IOException e) {
                        Log.e(MyGeocoder.class.getName(), "Error calling Google geocode webservice.", e);
                } catch (JSONException e) {
                        Log.e(MyGeocoder.class.getName(), "Error parsing Google geocode webservice response.", e);
                }
               
                return retList;
        }

Is this issue tracked in a separate thread? This issue is marked as
Status: WrongForum ?

Same issue[java.io.IOException: Service not Available]. kindly post any other method to get  Locality,Admin Area,Country Name,Postal Code,Address Line like using geocoder.

Is geocoder a part of Google Maps API or product? I don't understand what #44 says.

I can still reproduce this issue with my Galaxy S2 running 4.0.3. I need to reboot my phone once or twice in month. Google should have known this issue. Why do they leave this?

Hi,

I don't know where this issue is followed. I am very glad to see other people still have to restart their phones from times to times like me.

I have post my solution to get this, #51, here: http://stackoverflow.com/questions/18962020/reverse-geocoding-service-not-available-restart-device-not-solving-definitiv 
the idea is to use the geocoder but if it fails, i use a direct hit on http://maps.googleapis.com/maps/api/geocode/

@ #52 I am pretty sure that  geocoder is linked to googleplayservice

Thank you => #13 and #49

If a google developper can help us to know what is the status of this thread. The last update was from jbq but he does not work for android anymore.

Please star this feature request I created to add Geocoder support to the v2 mapping APIs in the Google Play Services library:

https://code.google.com/p/gmaps-api-issues/issues/detail?id=5935&thanks=5935&ts=1382028083

This helped me: Enter the proper url.
http://stackoverflow.com/questions/3505930/make-an-http-request-with-android

The problem appeared with Nexus-7 4.2.2 (2012) as well. Resolved by restarting the device! Has it been fixed by Google yet?

[Comment deleted]

Hey guys.

I've faced with the same problem. Geocoding was absolutely unavailable on two devices (Sony Xperia S26i and ZTE V889S).
But I opened a google maps app (v8.0) and placed a marker on a map... So the address was obtained correctly.
Then I rebooted a devices and launched my app. The geocoding works now. Miracle. :)

Tested on HTC one X 4.2.2. Exactly the problem and I have to reboot the phone. It works after the reboot, but this bug is quite ridiculous. Asking user has to reboot phone after installing app is really terrible

After rebooting it's works for my sony experia neo L

I reboted my Galaxy Tab 3 and it works! But how many times do we have to do that? Isthere another solution?

This is marked as WrongForum, your comments won't get any traction here, the bug has been logged int he correct forum here: https://code.google.com/p/gmaps-api-issues/issues/detail?id=6708

Let's try bump this one up a bit! We can't be asking users to restart their phones, and if you're going to code a fallback to hit the web API directly then what's the point in using the Android API at all.

I believe you just posted to the wrong forum. That's the Google Maps Api issue tracker. Who told you to post it there?

android.location.Geocoder is part of the Android SDK, not the Google Play Services lib.

Same problem on Wiko Cink Five.. Resolved by restarting the device too =)
How to explain that to my customers ?

#49's workaround helps a lot. Thanks!

I'm facing this same issue. I'm using Xamarin runtime though and some of the solution here don't explain the root issue. It's clearly the Android runtime (16+). Reboot has proven to work, but thats not really a solution, just terrible. Why exactly does this happen would be interesting to know. For now I'm just going to Catch Java.IO.IOException and inform the user there was an issue, reboot if you want the map to point to the correct address.

There are multiple threads about this issue on code.google.com (and most popular one is marked as WrongForum).

The problem is not rare, it happens all the time. After more than two years the only solution is to restart device.

Google - do you need some help in resolving this issue or are you not going to change that or you just don't read this because "WrongForum"?

Is there any alternative API we should use while this one is broken?

Please can we have more informations about this issue ?

First, this issue was marked as *WrongForum* because "the issue tracker it specializes in issues within the Open Source source code of the Android platform"

Then, in google maps issue tracker (https://code.google.com/p/gmaps-api-issues/issues/detail?id=6708), the issue was marked as *PostElsewhere* because "This is the issue tracker for the Android Maps API v2. The geocoder is part of the Android platform."

o_O

For now, the only solution is in #49's workaround

Someone (at Google) can tell us where the issue have to be posted and what is the state of this problem ?

Thx in advance

Not only #49

You can use new java client library:
https://www.youtube.com/watch?v=2s7UAscFUDw&list=TL79UxYgn5wA0

You can download it and check doc here:
https://developers.google.com/maps/documentation/webservices/client-library

[Comment deleted]

I guess java client library mentioned #71 will end up workaround stated in #49 in terms of solving issue discussed here. I'm now testing this workaround and I think;

1. It does not require API key.
2. Each Android device can use this API w/o hitting quota if you are replacing Android's Geocoder API which is what we are doing in the first place.

I hope Google will fix this issue but it may seem hopeless as it has been left unsupported for so long. And use of Google Maps reverse Geocoding API (=#49's workaround) looks only solution for me.

Solved after rebooting on android 4.2.2 - Huawei G750-U10.
Thanks.

In reply to comment #74 it's not solved by rebooting, it just sometimes makes the problem disappear for a while. And rebooting is not really a fix.

Is there another solution, like add code exception or make branches to show message when "list = gc.getFromLocation (mLatitude, mLongitude, 1); Address address = list.get(0);" is return null ?

this is not fixed in latest GooglePlayServices?

#77 Geocoder is not part of Play Services

reboot works fine thanks dude

reboot device again & again is not a solution, Google should provide exact solution for this

As #65 mentioned, android.location.Geocoder is part of android sdk! why is it marked as wrong forum? I have some of my users reporting this same issue. Please update

The actual implementation of the android.location.Geocoder isn't included in AOSP, which is why its marked as wrong forum - see http://stackoverflow.com/a/21860496/937715 for details.  The problem is there doesn't seem to be a proper forum to report the issue with the actual implementation of the Geocoder.

Related: https://code.google.com/p/android/issues/detail?id=214978

Good evening, excuse my English, it is translated.
I am working with BLU BLANK script. In a test application
In 2 phones BLU DASH L ANDROID 4.4.2 KITKAT, geodecode works, sometimes throws an exception
But then it is normalized (with maximum update -> mlocManager.requestLocationUpdates (LocationManager.GPS_PROVIDER, 0, 0, this);


On the other hand, on the BLU DASH C MUSIC ANDROID 4.4.2 KITKAT
Geocoder did not work for me. I tested it on 3 different BLU DASH C MUSIC and it did not work
In none, with permissions, data, internet, configurations.

The only solution to the problems that occurred in posting # 49 eufor ... @ gmail.com

Thanks god... final work after reboot my devices

Issue still there.
Kindly mark it as duplicate of: https://issuetracker.google.com/issues/35828055

Issue is happening in many devices, i think a fix from google will be better than the asking every user to restart their device.

bug still appears in numerous of devices. Every user should be asked to reboot the device. Some fixes from google would be nice! After 5,5 years...

Any solution available other than rebooting?

same issue in android : 5.1 ,  any news beside rebooting ?

For those that stumble onto this, the only workable solution that doesn't trigger the device to restart is to send a request to the Google Geocoding API to get your data (see comment 49 in this thread). Keep in mind that API now requires a tracking id so that you can be billed based on usage.

Correction, it appears that somehow the "solution" is now in #50 not #49.

Still facing same issue when trying to use geocoder class from android app. Calling webservice api solved my problem.

 But to call Geocoding Api we need to send Server key with either http or ip address restriction. The issue is we are using it from android app and the package restriction & SHA1 with Api key is not working and throwing an error "This IP, site or mobile application is not authorized to use this API key - Android App".

Struck with this from long time.

Any Help.. Thanks in advance

someone used <a href="https://gbchief.com/er-whatsapp-apk/">er whatsapp</a> on android 5.1?

Non-fatal Exception: java.io.IOException: Service not Available
       at android.location.Geocoder.getFromLocation(Geocoder.java:136)
Getting this issue in some devices and working fine in some devices.

Just over 3 days ago, the location service stopped working in an application developed with Android.
The error is: DEADLINE_EXCEEDED

what's the solution?
thank