Guillaume Bernos

Hello @Justus-M, thanks for reaching out, I couldn't reproduce the issue on our end with our example app. Could you provide a reproducible sample so I can have a look?

@Justus-M, thanks, should I understand it something on the customer side that blocked the token?

Based on the latest comment, it seems that a solution exists, I'll close this issue. Thanks dab246

Thanks for the report, have you tried in release mode?

Hi 👋 I see that you are using a much older version of firebase_core than the current one, can you update to `firebase_core: ^2.27.2`

Hello @keithcwk, are you testing this in release mode instead of debug? Notification will sometime not be properly passed through when using debug mode.

Hello @matt-hall-zory, thanks for the report. According to the documentation: https://firebase.google.com/docs/auth/extend-with-blocking-functions?gen=2nd#understanding_blocking_functions, ``` Anonymous and custom authentication do not trigger blocking functions. ``` So it would make sense that the function...

I've run it internally and we recently had some changes around this function, see here: https://github.com/firebase/firebase-ios-sdk/issues/12313

Hello @matt-hall-zory, we had a couple of fixes around this in the Emulator as well as in the Native SDKs. Are you still seeing the same issue?

Hello @aemelyanovff, thanks for the report. We'll have a look.