-
Notifications
You must be signed in to change notification settings - Fork 3.9k
UNAVAILABLE: Unable to resolve host #8860
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
Comments
We might need more logs/strack traces to know the issue. I am suspecting dns resolution problems in your environment, or dns cache. If you can produce it again, could you provide more logs. |
@YifeiZhuang I'm seeing what is probably the same, in the context of https://github.com/firebase/firebase-android-sdk, which use gRPC. With logging enabled, they seem to be doing the right thing:
after which they can succesfully send data to the backend again. Here's the entire log of a session I just did. It took 57.818 seconds for it to realize that it was possible to connect: The entire log, click to expand
Apologies for posting this here, but I believe this is primarily an issue with gRPC and not their SDK. Also, I should mention that this behavior is disastrous in the context of a cloud database. It should always be able to connect immediately when coming out of standby. 😅 Ps. Here's the class that's doing the gRPC logging for posterity: https://github.com/firebase/firebase-android-sdk/blob/ac3276ce7d5f5181b1c419731495eb88a98537af/firebase-firestore/src/main/java/com/google/firebase/firestore/remote/GrpcCallProvider.java Pps. Here's an old but interesting issue that seems very related: #4028 |
This might be related to #8850 |
Closing since we know #8850 was very similar problem and it likely addressed this. The delay before detecting network is good is because the channel is doing retry attempts with exponential backoff. The exponential backoff maxes out at 2 minutes which seems to agree with the observed behavior. If the other fix turns out not to address this, comment and this can be reopened. |
build.gradle:
I have used
ManagedChannel
for grpc call in android:I'm getting
unable to resolve host
in android when I'm opening the app from the background in some time. My network connection is good also HTTP requests are working by retrofit. The only problem is in the grpc call. After reopening the app everything is working fine as expected.Is there any way to handle the above issue??
The text was updated successfully, but these errors were encountered: