Angular ServiceWorker interferes with Firestore's network requests ("Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds" log warning).

[Brahmarishi]

[REQUIRED] Describe your environment

• Operating System version: MacOS 10.13.4
• Firebase SDK version: 5.0.4
• Firebase Product: Firestore

[REQUIRED] Describe the problem

Firestore fails on production mode.

[2018-06-04T06:11:47.859Z] @firebase/firestore: Firestore (5.0.4): Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds.

This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.

Steps to reproduce:

build project using ng build --prod and served in firebase hosting firebase deploy --only hosting

Relevant Code:

Firestore fails to start.

this.afs.collection('users').doc<User>(user.uid).valueChanges().subscribe((data) => {
    console.log(data)
};

undefined -> console.log(data)

The version used is firebase: "5.0.4" with angularfire2: "^5.0.0-rc.10"

[JancoBH]

I have the same problem, I have no idea how to solve this but it happens only when I use my personal laptop (to see the error I need to refresh the page and change the browser tab to any other, after 10 seconds or more, I back and I see the error) , when I try to do the same in the PC of my work I can't see the error again.

This is a big problem because I use Hotjar and I see many people getting the same error when the firestore data are not presented.

I'm Using Angular 6.0.3, angularfire2 5.0.0-rc.10 and firebase 5.0.4

[mikelehen]

@JancoBH That is not really the same problem, since the original issue was caused by build minification. It sounds like your problem might be related to your browser throttling the page when it's in a background tab, causing our Firestore connection to time out. If you want to pursue this further, it'd be helpful if you could open a brand new issue and include whatever details you have about customers hitting this (e.g. verify that the problem is only when in a background tab, etc.).

For what it's worth, Firestore will continue to connect to the backend, so as long as you're using an onSnapshot() listener, you will receive data once it successfully connects.

[sujit13666]

same problem here in react native when using firestore.

[jbsness]

same here using vue.js and vue-firestore

[mikelehen]

Thanks for the feedback. Unfortunately, reporting that you get this log message without any additional context is not actionable.

To be clear:

1. The log message is 100% normal in certain circumstances.
2. The issue reported by @Brahmarishi sounds like an environment issue and isn't indicative of a problem in Firebase or Firestore. I'm only leaving this issue open because if the problem is identified, it's possible we could implement some workaround or provide advice for other devs that run into this.

@sujit13666 React Native is a whole different beast. We've had a number of issues with React Native and have fixed some in Firestore and some in React Native. Please make sure you're using the absolute latest versions. You may also want to look at #638 (comment) which describes a recently-discovered issue with react-native-image-picker. If none of this solves your issue, please open a brand new issue with minimal repro steps so we can reproduce the problem and investigate.

@jbsness Can you clarify that you are seeing the exact same symptoms that building with ng build --prod causes you to get this error? If not, please open a brand new issue with minimal repro steps and as much detail about your environment as you can provide so that we can reproduce the issue.

Thanks!

[altaired]

Also getting the following error from multiple computers and network connections:

@firebase/firestore: Firestore (5.0.4): Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds.
This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.