CubitListener behaviour skips(1) about cubit

[narcodico]

I've created a quick sample to illustrate this common request, maybe others will also find it useful.

You can check it out here 🎉

[Manuelbaun]

HI @RollyPeres,
yes, you are right, it makes totally sense now. I also found out, that when I would change the skip to 0, then I get another undesigned behavior, in the sign-in/signout flow. So it must be some architecture-related issues.

Thanks for pointing it out. I will look into the example you've posted. Since I am also using the Auto_route package, I will have to look at how I can make it work together.

[felangel]

Hi @Manuelbaun 👋
Thanks for opening an issue!

Cubit is still async and this isn't specific to cubit (you can have a race-condition with listeners with bloc as well). I would highly recommend lifting your listener up in the widget tree to be above where the method is called. That guarantees the listener is mounted before anything has happened.

If you're still having trouble, it would be great if you could share a link to a sample github repo which illustrates the problem you're having. Thanks! 👍

[narcodico]

Hi @Manuelbaun 👋

The listener is by design implemented in such a way that it will only react to state changes after it is mounted into the tree, since it doesn't make sense to react to the last known state since that might be obsolete by the time the listener subscribes to the stream of states.

Your issue raises from your architecture. Your CubitListener<AuthCubit, AuthState> should be placed globally instead of scoping it to your splash screen, because you always want it to be ready to react to state changes in your authentication.
A good place to provide it would be inside MaterialApp's builder.
You can check out this example and adapt it to cubit.

Hope it helps 👍

[Manuelbaun]

I looked into the example and I could refactor authentication as you suggested and provided it to the builder in the MaterialApp.
However, the example uses bloc with the async event dispatch, but Cubit uses methods (sync).

But the issue remains:
I need to call the method checkIfAuthenticated of the AuthCubit after the CubitListener listens to the AuthCubit. Then the listener would be triggered properly and I can navigate to another page.

But currently, there is no way, to find out, when the CubitListener is mounted to the tree. So if call the checkIfAuthenticated method just before its mounted, then I will not be able to navigate to another page.

I could use a time delay, but it a dirty hack and potential for a race condition.

Do you have an idea of how I can manage that?