-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Dns$Companion$DnsSystem.lookup No address associated with hostname #8481
Comments
It seems likely that this issue is related to Firebase sending requests while the app is in the background. Some Android OEMs might block the internet connection for apps running in the background. As a result, the system's DNS lookup could cache failed requests, causing the first request after the app returns to the foreground to fail due to the cached DNS entry. In theory, the failed DNS lookup cache has a TTL of around 2 seconds, so any request made after this period should be fine. For more context, you can refer to the discussion in this related Retrofit issue: Retrofit issue #3915. |
Hi... Same problem here started 12th July. I think @ilkcansaricicek mean to say July and not June, accordingly to his chart. This is really weird and we're trying to find the root cause of this also but without success. Take a look at the error that lead to crashes 👍
If anyone have workarounds or idea of how to fix this I would appreciate it. Thanks |
@jricardooliveira Even with this failure, it shouldn't be leading to crashes. Are you missing some error handling around these requests? Or is this outside your control? |
I'm having the 'Unable to resolve host "api.mycompany.com": No address associated with hostname' error too for a while now too. |
Likely the same issue as firebase/firebase-android-sdk#6419 Closing as not an OkHttp issue. |
Hello,
I published my application on June 12. And this version, I upgraded okhttp library from 4.9.1 to 4.12.0. I am displaying a lot of the following error in try-catch block in firebase. (no changes were made on the server side)
Is there anything I should check?
Thanks
The text was updated successfully, but these errors were encountered: