Same issue as https://github.com/invertase/react-native-firebase/issues/1441
We get a lot of Firestore service unavailable errors we even have it retry once a second for 10 seconds doesn't go away.
Is this a React Native Firebase bug or is it Firestore itself and I need to contact Google?
using "react-native-firebase": "5.5.5",
Error: Firestore: The service is currently unavailable. (firestore/unavailable).
at createErrorFromErrorData(/Users/vsts/agent/2.158.0/work/1/s/node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:155:36)
at apply(/Users/vsts/agent/2.158.0/work/1/s/node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:104:31)
at __invokeCallback(/Users/vsts/agent/2.158.0/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:414:13)
at fn(/Users/vsts/agent/2.158.0/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:127:12)
at __guard(/Users/vsts/agent/2.158.0/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:314:9)
at value(/Users/vsts/agent/2.158.0/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:126:10)
at [native code] value(:0:0)
anyone? this happened a lot today. firebase support won't help they say the problem is the library
I can't think of any reason why it would be us. We simply pass some data over to native land and then call the Firebase SDKs with that data. We'd really need some networking logs to really understand what's happening, but that needs to come from Firebase/Google.
@Ehesp firebase is saying "For libraries leveraging the Web SDK, you may enable debug logging using this line of code:
firebase.firestore.setLogLevel("debug");
Debug logs provides access to the internal state of the SDK, so this information would be valuable to us. Note that the React Native library may expose this method using a different syntax."
does this use the web SDK...? is there another way you have to turn on logging? I can try doing it
Your best bet would be checking the native logs in Studio/XCode for messages, as we can only relay errors back.
ok will look - confirming firebase.firestore.setLogLevel("debug"); works?
Hello 馃憢, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?
This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.
it still happens a lot
Hello 馃憢, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time. Has this issue been fixed, or does it still require the community's attention?
This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this is still present in the latest release, please feel free to create a new issue with up-to-date information.
It isn't fixed
This issue still happens
@dgobaud
did you solve this issue?
no - planning to get rid of react native seems to be thing to do
oh, sad to hear that
I'm facing the same issue on my App in production now and then.
Non-fatal Exception: UnhandledPromiseRejection [firestore/unavailable] The service is currently unavailable. This is a most likely a transient condition and may be corrected by retrying with a backoff. <unknown>
Would be great to find a workaround soon.
Anyone found a solution for this issue? I am facing this issue in flutter firestore .
@findnizam so far it seems to have always come down to someone actually not having network (stable, and all the way through to google services in the cloud)
Anyone found a solution for this issue? I am facing this issue in flutter firestore .
I solved this issue by updating google play services in Emulator.
Still happens with
"@react-native-firebase/app": "^8.4.2",
"@react-native-firebase/auth": "^9.2.2",
"@react-native-firebase/firestore": "^7.8.1"
This issue still happens
Most helpful comment
Still happens with
"@react-native-firebase/app": "^8.4.2",
"@react-native-firebase/auth": "^9.2.2",
"@react-native-firebase/firestore": "^7.8.1"