Reopen of #4907 Crash due to FirebaseNetworkException: A network error (such as timeout, interrupted connection or unreachable host) has occurred.

[janseeger]

The bot has closed and marked the original issue as stale and locked further interaction. I'm reopening this now and am willing to post daily updates to keep the bot away if needed.

The issue still persists.

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[janseeger]

Feel free to close this one after the other one has been reopened and most importantly unlocked for future comments.

[argzdev]

Hi @janseeger, thanks for reaching out. Is the issue similar to the author where firebaseAuth.currentUser?.getIdToken(forceRefresh = false) is causing the network failure? Can you also share what Firebase Auth version are you currently using? If there's any chance you could share a minimal reproducible example, it'll really help us out a lot. Thanks!

Update: Follow up question, are you also using the GitLiveApp for Firebase Auth?

[janseeger]

Hi, we did experience this with several versions (Currently 21.3.0) and we don't use the GitLiveApp.

What we do have noticed however: Firebase works offline just fine but starts to fail when the device has been offline for some time (in our case often after lunch break).

[argzdev]

I see, that's interesting. So is the following steps to reproduce this issue correct:

1. Firebase user logs in
2. While signed in, leave app for sometime until it dozes or goes to sleep
3. After sometime, wake phone up while app is still open and user is still signed in
4. Will start receiving FirebaseNetworkException in the logs. (Or is there any extra steps or triggers before experiencing the exceptions?)

[janseeger]

To point 2 and 3: We don't know if it is because the app is in doze or sleep. It also crashes when force closing and manually reopening the app in offline state. (Reopening the app after the crash immediately crashes with the same stack trace again)

To 4. Yes, once in a while our app crashes with the given stack trace without our code being involved.