fix: `BlocConsumer.listener` is not being fired about bloc HOT 5 CLOSED

I am using navigation 2.0 with the go_router already, I will explore more your suggestion, thanks.

from bloc.

Hi @feinstein 👋
Thanks for opening an issue!

This is happening because the BlocConsumer's listener only fires for state changes after the listener is mounted. In this case, you are calling bloc.load in initState before the BlocConsumer has mounted and the state change happens before listener starts listening. Hope that helps!

from bloc.

Hi @felangel thank you for the clarification. I think this should be added into the docs then.

I am adapting Google's recommended Android App Architecture, using bloc at the UI layer. My cubit acts as a View Model, making the decisions for the UI. Once the decision to navigate is made, the cubit emits a new state with a flag, so my View, in Flutter, can navigate (using a listener).

In this code, I want to navigate as soon as I get the result on load, but I understand now this won't be possible using bloc, unless I do some hacks :/.

Do you think it's worthy to make the listener fire, after it was mounted, if the state is different then the cubit's initial state? I imagine this might add some extra complexity, but at the same time it will match the docs and make this edge case work.

from bloc.

Hi @felangel thank you for the clarification. I think this should be added into the docs then.

I am adapting Google's recommended Android App Architecture, using bloc at the UI layer. My cubit acts as a View Model, making the decisions for the UI. Once the decision to navigate is made, the cubit emits a new state with a flag, so my View, in Flutter, can navigate (using a listener).

In this code, I want to navigate as soon as I get the result on load, but I understand now this won't be possible using bloc, unless I do some hacks :/.

Do you think it's worthy to make the listener fire, after it was mounted, if the state is different then the cubit's initial state? I imagine this might add some extra complexity, but at the same time it will match the docs and make this edge case work.

I highly recommend checking out something like package:flow_builder if you want to do navigation based on state changes. You can also just the Navigator 2.0 pages API directly if you prefer not to introduce an additional dependency. I'd prefer not to change the behavior since it would be a potentially very disruptive breaking change and the issue you're facing can be resolved using a declarative navigation solution. Hope that helps!

from bloc.

I am using navigation 2.0 with the go_router already, I will explore more your suggestion, thanks.

Sounds good! You can refer to the Firebase Login Example for a reference.

from bloc.