Incorrect behavior with FragmentPagerAdapter and Dagger about moxy

[Dosssik]

Hi @bitvale!
This is not a library issue.
If you use Moxy without Dagger, then presenter lifecycle is pretty simple: presenter will be alive until fragment exists and it will survive fragment's recreation. When u'll pop fragment from the back stack - presenter will be destroyed.

If you use Dagger for providing presenter then you have to manage presenter lifecycle manually, cuz you create presenter by your own. In your example you create new presenter each time when fragment calls providePresenter(). That's why you have couple of presenter's instance. You can configure Dagger to provide singleton instance for your presenter. And, sure, you will be responsible to destroy presenter when you will no need it - be carefull cuz Dagger could hold the reference to your presenter. Subcomponents could help there...
All this headacke gone if you provide presenters by default library's way, without Dagger ;)

Cheers

[bitvale]

But my presenter is annotated with custom annotation and is a singleton. And new instance of presenter is not created each time fragment calls providePresenter(). I think if I use @ProvidePresenter then presenter is attached to Moxy life circle and Moxy is responsible to destroy them, not it?