Guillaume Bernos

@ariefwijaya As pointed in the issue, this thread is for tracking support of Flutter own [Background Isolates](https://medium.com/flutter/introducing-background-isolate-channels-7a299609cad8)

Currently, we rely on both ways communication. As long as Flutter will not provide communication from the host to Flutter, it will probably stay in this state.

The latest version of firebase_core 2.9.0 contains 10.7.0. Let us know if it helps.

Thanks for the info. Unfortunately, it's not enough to reproduce the crash on my end. I see that this error has already been reported on iOS: https://github.com/firebase/firebase-ios-sdk/issues/2748 and is tied...

Hi @jhenriquedsilva, I think it may be happening because custom keys are global and associated with an exception only when crashes are sent to crashlytics. Could you try to add...

Hello, it has actually been released for a couple of time: ``` Stream snapshots({ bool includeMetadataChanges = false, ListenSource source = ListenSource.defaultSource, }); ``` I'm closing this :)

@darshankawar Do you see the issue on the emulator or prod? I've checked the code, and we correctly use the values provided by the native SDK

I've opened an issue here: https://github.com/firebase/firebase-ios-sdk/issues/10656

Hello, I've checked in the latest version and I'm not reproducing this issue. I'll close it but feel free to open a new issue if it's still happening.

Copied to: https://github.com/FirebaseExtended/firestoreodm-flutter/issues/29