Action for EventEffect or NavigationEffect is called twice per trigger. about compose-state-events HOT 4 CLOSED

Hi @TommyVisic,
unfortunately I was not able reproduce the described behaviour. Could you please send an example project where the bug happens? I would be really interested looking into that behaviour.

Setting the onConsumed as a reference or as a lambda definately makes a difference in terms of recomposition. But the library needs to be save to use even with a lambda I think.

Btw: Was the code snippet above just a random example? I think you dont need to trigger this close event via the views state if it is just a direct reaction to a users button click.

from compose-state-events.

StateEventExampleApp1.zip

Here's a sample that reproduces the double event. It looks like the key is 1) observe a MutableStateFlow and 2) call navController.popBackstack in the StateEvent action.

Yes, this is pretty much a random example. But in our case, we do indeed involve the view model in the close event because we have to do some work before we want to actually close the screen. Basically it's a "save and close" kind of action.

Thanks for your response!

from compose-state-events.

@TommyVisic Thank your for your example project. I was able to reproduce your described behaviour. Looking into it.

from compose-state-events.

Fixed in release 2.2.0

from compose-state-events.