Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Component used: Fragment Version used: 1.3.0-alpha06
Right now,
setMaxLifecycle()only supportsLifecycle.State.CREATEDor higher. It would be nice ifsetMaxLifecycle()could also supportLifecycle.State.INITIALIZINGonly for Fragments that have never moved aboveCREATED- i.e., only something that could be set alongside the Fragment being added to theFragmentManager.This would allow developers and libraries built on top of fragments to keep fragments only at the attached state without going through
onCreate().