IssueTracker

Alright, thank you! Maybe this part of the documentation could be changed, then: The onCommit effect is a lifecycle effect that will execute callback every time the inputs to the effect have changed.

Is there a way to launch an effect that only runs once, then? What I am trying to achieve is get a callback for onDestroy of the navEntry's lifecycle, and currently my code subscribes several times to that lifecycle instead of once.

Oh well, what I am trying to do is precisely substituting the android ViewModel for a platform independent one.
I think there should be an option to opt out of using ViewModels, as they might not always make sense (when orientation change is disabled or when config changes are manually handled without recreating the activity).

Thank you! After your first answer I thought about trying this and it works.

It is hacky though, as you said. It would be better having a better option at some point :) should I create a feature request, instead, for this?

Since what I am trying to achieve is precisely substitute android viewModels, what I do is add a subscriber to the navEntry.lifecycle and call the onCleared equivalent in the on destroy event. It works for me but I have not tested it thoroughly. Is there a reason why this should not work under some circumstances?

Since with compose it is quite easy to handle config changes manually, if you decide to go that road it makes no sense having an android viewModel, as it is designed precisely to survive config changes. For that reason I think it would make sense that the navigation component offered an alternative to using viewmodels (either through an alternative class or, even better, allowing us to use anything). That would be more lightweight and maybe not need to be built by the system through a factory.