Making a Fragment Lifecycle Destroyed should not be allowed by FragmentScenario or setMaxLifecycle [170765622]

Fixed

Bug

androidx-bug-bounty

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Oct 14, 2020 06:58AM

There are no use cases when we should allow a fragment's Lifecycle to be moved to DESTROYED other than when the fragment is actually destroyed.

Therefore, you should not be able to setMaxLifecycle() to DESTROYED through a FragmentTransaction, initialize a FragmentScenario with DESTROYED, or move a FragmentScenario to the DESTROYED state using moveToState().

Doing any of these things should throw an error.

Comments

il...@google.com <il...@google.com> Oct 27, 2020 11:40PM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #2Nov 20, 2020 08:28PM

Yigit, do you have time to fix it?

reemission of the same liveData is racy

ap...@google.com <ap...@google.com> #3Nov 20, 2020 10:09PM

yea i'll take it.

jb...@google.com <jb...@google.com> #4Nov 23, 2020 08:13PM

Marked as fixed.

Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.

Issue 170765622

Description

Issue summary

Comments

il...@google.com <il...@google.com> Oct 27, 2020 11:40PM

ap...@google.com <ap...@google.com> #2Nov 20, 2020 08:28PM

ap...@google.com <ap...@google.com> #3Nov 20, 2020 10:09PM

jb...@google.com <jb...@google.com> #4Nov 23, 2020 08:13PM

Add comment

Issue metadata