Denver Coneybeare

Results 297 comments of Denver Coneybeare

> @dconeybe are you aware of the official flutter plugins usage of the C++ SDK ([firebase/flutterfire#10496](https://github.com/firebase/flutterfire/pull/10496))? If not, could this influence the plans to take this SDK out of beta?...

@KoryNunn Thanks for the update. My update is that work on the manual overriding of the node/browser detection is still a work in progress; however, it's taking a while due...

Update: A new feature to allow users to specify their environment as "node" or "browser" to override Firebase's runtime environment detection and force the SDK to act as if it...

FYI the fix has been released in version 9.18.0 on March 16, 2023: https://firebase.google.com/support/release-notes/js#version_9180_-_march_16_2023

@50an6xy06r6n Please open a new issue at https://github.com/googleapis/nodejs-firestore/issues/new?template=question.md for the specific question you have. That will help investigate your specific issue without adding tangential discussion to this feature request. Thanks!

> Do we have to wait for the fix made in `firebase/firebase-js-sdk` to be released here? Yes. We are _planning_ to have the change released here in the coming months,...

Hi @sspogra. I have poured over the code and cannot find an explanation for the crash that you are experiencing. The only explanation that I can think of is that...

Another crash report by the same customer that appears to be the same root cause: https://github.com/firebase/firebase-ios-sdk/issues/10691 Here is the stack trace: ``` Fatal Exception: std::__1::system_error recursive_mutex lock failed: Invalid argument...

Yet another crash report by the same customer that appears to be the same root cause: https://github.com/firebase/firebase-ios-sdk/issues/10697 Here is the stack trace: ``` Crashed: com.google.firebase.firestore 0 libsystem_kernel.dylib 0xb160 __pthread_kill +...

@sspogra Thank you for the continued reports. I have no doubt that this crash is still plaguing your app. Note that the stack trace of your last comment shows the...