bluelinelabs / bluelinelabs/Conductor
Unexpected lifecycle after pushing a Controller while app is in background
- Dominant language
- Java
- Stars
- 3.9k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
Hi, If I add a Controller while app is paused, the lifecycle of the pushed Controller is in my opinion wrong / unexpected.
I add it via this, and hit home button before somethingAsync callback is called
```
Activity {
fun onCreate() {
somethingAsync {
router.pushController(..)
}
}
}
```
Observed lifecycle:
```
ctor
onCreateView
onDestroyView
onAttach
```
I'd never expect attached controller to have null view. Is this by design?
Contributor guide
Research direction
Start with the Activity.onCreate callback and router.pushController call described in the report; reproduce them after pressing Home and compare the observed ctor, onCreateView, onDestroyView, and onAttach sequence. Done means the expected lifecycle behavior is established and the reported sequence is either explained as intentional or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100