Prevents recursively moving activity to a new expanded container
When an activity should be expanded, the activity is moved to a
new expanded TaskFragmentContainer and the same container was
splitted with the SplitPinContainer in the same WCT. However,
the activity may be relaunched afterward when updating the
TaskFragment bound (or could also due to insets changes). In
that case, the activity will be resolved to move to a new
expanded TaskFragmentContainer again while Activity#onCreate
is called. So, TaskFragments are created (and removed) repeatedly
for the expanded Activity.
This issue is not reproducible if the activity can handle the
configuration change.
Do nothing if the expanded activity is already in a standalone
container and split with another pinned container.
Bug: 355595391
Test: verified locally with sample app
Flag: EXEMPT bugfix
Change-Id: I8d92788287d72e1a58d1ad383c25585ea7fc4a19
1 file changed
