Guillaume Bernos

@deffs I'm wondering if it's due to this setting in the console:  If the user has already created an account, you might have to...

As noted [here](https://github.com/firebase/flutterfire/issues/11581#issuecomment-1798220080), I cannot reproduce the issue, do you mind providing a full reproduction example so I can check what's going on? Thanks

Hi @deffs, thanks for the investigation, that is probably why I wasn't able to reproduce this issue with our own Microsoft account. I'll see if I can find a way...

I'll close this issue since it's blocked by Firebase SDK and we will not be fixing this.

Hello @collinjackson For AppCheck the instance is only a getter ```dart /// Returns an instance using the default [FirebaseApp]. static FirebaseAppCheck get instance { _instance ??= FirebaseAppCheck._(app: Firebase.app()); return _instance!;...

Hey @adar2378 It seems related to how Flutter is handling waking up the dart Isolate. It keeps firing up the main even thought this is just handling the background notification....

I think it was fixed in the latest macos-13 runners for GitHub action.

The use case for FlutterFire is to create a method channel per request from the user and close the native listener properly when the subscription is closed. To create the...

Thanks for your help. I think we’ll just workaround this.

Thanks for investigating, I'll have another look on my end