IssueTracker

Same problem, but not only with simulator.

Suffering same issue.  java.io.IOException: grpc failed after calling geocoder.getFromLocation()

It happens on all emulator APIs I've tried (API levels tested were 23, 24, 25 using x86_64 Google APIs images and API 26 using x86 Google APIs )  Real devices seem to work fine.  Definitely a more recent issue since my app is many years in development and this was not always a problem.  My app falls back to use https://maps.googleapis.com/maps/api/geocode/json?latlng=... but this is a quota limited API and slow.

This is working for me on all of my emulator APIs that were previously failing a couple of days ago (21 through 25). Just curious - does anyone know how the fix was delivered? I didn't manually update my Android software.

I can confirm that the problem has gone away for me also without any change to my virtual devices.

Suffering same issue. java.io.IOException: grpc failed after calling geocoder.getFromLocationName().
Note that the other method call (getFromLocation()) is working fine. From what I noticed, the issue seems to be related to Google Play Services installed on the device. I tried using the geolocator with PlayServices 11.5.09 and I get the grpc failed error. If I rollback to the factory version of Play Services (i.e. uninstalling updates), Geocoder's method "getFromLocationName" works again.

I have checked back, as #4 mentioned, the problem on the emulator seems to be fixed and must been a server side issue or as #6 mentioned a problem with Google Play Services. I haven't had problems on my real device, but results might differ, as I was testing using Huawei P9 Plus.

Thank you for reporting this issue. Can you please provide the below requested information to better understand the issue:

Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Hi ar...@google.com, I too have this same issue. You shall refer to the screenshots shared by #1, it is exactly where the issue is coming. For me, this issue is inconsistent as it is working in some of Android 5.x devices and not in other devices. My customers started complaining this issue and things are going crazy here. Searching for a solution, pls help. I think it is not working when the play services is updated to latest version.

I am not sure of this will help a lot, but there might be one of the following reasons that caused this problem (at least in my case):
 So, I noticed that, this problem started to happen after :
 - started my app on an emulator (before I had no problem with this)
 - or from the last google-services update (did work fine before)

I am in this kind of problem right now also, but it fails on real device.
Notice: It doesn't always fail, just sometimes (kind of randomly, for instance I had a case in which it started working after a fail, without any app / device restart)

I also got same issue.. LocationManager.getFromLocation(latitude, longitude,maxresults,params,results ) gives gprc failed on Oppo real time mobile device.If you get any solution, please give me the answer.
.

I am running into the same issue as well. If I run it on simulator then no issue, but if I run it on device then there is an issue. I am using Samsung S7

This issue is really crazy, is there any other alternative solutions?

I am running into the same issue as well on real device, Services Google Play Version 11.9.75 ( 240-182402865)

please try to fix this blocker issue ASAP.
as there is lot of people complaining about it.

I am running into the same issue as well on HUAWEI PRA-LX1 (Android 7.0, API 24).

Hi all, I have been inactive on this thread for sometime, but i guess the fix hasn't really been implemented for all environments based on the comments here. Please include your current google play service version and as much environment information possible to help find a solution or workaround of possible. I hope that is issue is escalated to either a P1 or P2 issue.

Facing same problem on Samsung J7 2016

ar...@google.com, is...@google.com

Here are the exact steps to reproduce this problem. There are totally 3 ways to reproduce the same problem.

Case 1:
1- Restarted my phone Redmi 3s.
2- Turned GPS On, Wifi On and the Mobile Data Off.
3- Wifi is not connected to any Network. So basically No Internet Connectivity.
This led to IOException: grpc failed.

Case 2:
1- Turned Wifi On and GPS, Mobile Data both were Turned Off.
2- Wifi is not connected to any Network. So basically No Internet Connectivity.
This led to IOException: grpc failed.

Case 3:
1- Turned On Wifi, GPS and Mobile Data.
2- Wifi is not connected to any Network and also Mobile Data has Low or Mostly No Connectivity.
This led to IOException: grpc failed.

Case 4:
1- Turned Off Wifi, GPS and Mobile Data.
This led to IOException: grpc failed.

Case 5:
1- Turned Off Wifi and Mobile Data while GPS was Turned On.
This led to IOException: grpc failed.

Google Play Services: Version- 14.3.66 (040406-213742215)
Mobile Phones Used: Redmi 3s(Android 6.0.1-Marshmellow), Oppo F1s(Android 5.1-Lollypop)

The issue seems to be related to the connection speed, you can reproduce it easily using the Emulator, set Network type to GPRS, you get every time an grpc failed exception.

I'm facing same problem. how to resolve that grpc failed and what is  the common reason to have that result?

same..

change the emulator's network type i just changed it to LTE and its working

i'm using nokia 5.1+ (Pie) and get same error

Same. This frequently happens on real devices as well.

same issue on pixel 2 XL

Same issue on LG-D802 with Android 4.4 and Google Play Services.Maps 16.1.0. Works correctly an Galaxy Nexus and various emulators.
minSdkVersion 14
targetSdkVersion 28

Same issue on Nokia 6
AndoridAPIVersion : 27

same on
minSdkVersion 15
targetSdkVersion 28

Same issue on Moto e4.  Tried geocoder as a service and the same issue.

same

Same issue. api 29, pixel emulator

"java.io.IOException: grpc failed
        at android.location.Geocoder.getFromLocation(Geocoder.java:136)"

The same issue.
Someone please helps!

I am facing the same issue -> Service Not Available (Failed to fetch address)
    java.io.IOException: grpc failed

same issue on pixel 2 android 10 device, target sdk is api 28

Same issue here.

2 years and still no fix?

I had to turn on Wifi on the emulator to work.

I have the same issue on multiple devices, Samsung S5, A30, A50 and A50S, with different version of API. I used AsyncTask and split it from main thread but it still gives me this error:

W/System.err: java.io.IOException: grpc failed
W/System.err: at android.location.Geocoder.getFromLocation(Geocoder.java:136)

Same problem

Google API: grpc failed Same issue

Same problem.
At Pixel 2 API 28

Same problem


Huawei p9 Lite

minSdkVersion 21
compileSdkVersion 28
targetSdkVersion 28

play services version :
com.google.android.gms:play-services-location : 17.0.0

Error : java.io.IOException: grpc failed

@Sebastianbaar
Sir,
       I'm getting grpc failed while accessing the GeoCoder, can you help me Sir..
i have been tracking your post about these on few years back, but still i could not fix it.
Sorry about my english...

Suddenly got this issue on Android 10. I have stable internet connection, so it doesn't help. And got this issue first time a week ago, so it's something new.

Same Problem

Honor 9 Lite
Android 9.0.0

minSdkVersion 21
compileSdkVersion 28
targetSdkVersion 28

play services version :
com.google.android.gms:play-services-location : 17.0.0

Error : java.io.IOException: grpc failed

compileSdkVersion 29
buildToolsVersion "29.0.3"

minSdkVersion 21
targetSdkVersion 29

Device - Nokia 6.1 plus
Android -10

implementation 'com.google.android.gms:play-services-maps:17.0.0'
implementation 'com.google.android.gms:play-services-location:17.0.0'

issue - It used to work initially but all of a sudden it is not working. Trying to figure it out from past 5 hours but didn't find proper solution. Any solution would be appreciated.

java.io.IOException: grpc failed

I am facing this issue also, please let me know if there is any solution.

I m facing this issue on real device.

Yes, this exception is thrown sometime and I don't the reason behind it.

same here

same here on emulator and real device in production. switch airplane mode to off then on resolve the issue but I can't tell my user to do it every time it happens.

same here......

Thank you for your feedback.  We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.

i Got the same problem with API 28 on emulator ! :(:( sometimes works.. sometimes not..

same here... i finished my project yesterday 12/8/2020 and everything worked fine as i expected but a day after  (today 12/9/2020)  i get that error whenever i try to retrieve data from geocoder

just had the same problem, I tried all the recommended stuff and nothing. But I deleted the current emulator and created a new one and it worked, I guess the geocoder uses some memory and the previous emulator was full or something.

Hi there,
facing the same issue in irregular cycles on real devices too, sometimes the application works fine in one go, while other times it takes multiple attempt of re-tries. Any sort of help is highly appreciated. thank you!

Any solutions ?
On real devices it happens a lot ..

This is still a problem

Still a problem!

Even doing it in a background thread, no matter what I still got crash !
PLEASE GOOGLE FIX THIS

Hi All,

This issue thread has already been closed, therefore google might not see your comments.

Unfortunately I don't have access to the code and time to replicate back the issue its been quite long. As #55 has reopened the issue https://issuetracker.google.com/issues/168043749 please instead comment and provide the necessary information google is requesting over there.

This is still an issue even on real devices and it currently happens 90% of the time.