Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When to destroy activity's presenter
See original GitHub issueWe need a more reliable way to detect when to destroy activity’s presenter.
Here is where the issue that started the discussion: https://github.com/konmik/nucleus/issues/42#issuecomment-204233175
TL/DR: activity’s finish() can be called some time after onPause, so this code will leak the activity’s presenter: https://github.com/konmik/nucleus/blob/master/nucleus/src/main/java/nucleus/view/NucleusActivity.java#L76
Possible solutions:
a) Leverage retained fragments. This will solve the presenter destruction issue but we will leak background tasks sometimes.
b) Extend PresenterLifecycleDelegate lifecycle to explicitly call onDestroy.
c) Install system-wide lifecycle listener registerActivityLifecycleCallbacks.
Issue Analytics
- State:
- Created 7 years ago
- Comments:51 (27 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
3.0.0-beta is on maven
Hey, can we use isChangingConfigurations() instead of isFinishing()? So presenter will NOT be destroyed only if it is configuration change incoming.