Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
What version of Activity are you using? Upgrading your Activity dependency 1.7.2
which also depends on Lifecycle 2.6.1
should resolve this.
il...@google.com <il...@google.com> #3
Thanks. I stumbled upon https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:activity/activity/src/main/java/androidx/activity/ComponentDialog.kt;bpv=1;bpt=0
And see it was fixed in commit 602bac6c67b589d11f8f4d1441a4aec4dca0ee49.
Ill wait to upgrade until after that commit is in the stable release.
And see it was fixed in commit 602bac6c67b589d11f8f4d1441a4aec4dca0ee49.
Ill wait to upgrade until after that commit is in the stable release.
Description
Component used: Fragment Version used: 1.3.0-alpha04
FragmentScenario's
moveToState()
calls through toActivityScenario
'smoveToState()
, which means it is not possible to move to theSTARTED
case prior to API 23 and strongly couples the Fragment to the underlying Activity's state.It would be nice if for its implementation of
FragmentScenario
could be entirely decoupled from changes in the Activity's state by usingsetMaxLifecycle()
moveToState()
.