9d4244ee6f80a3cf4c11cdc76202f26aff6110fb
This can happen in two cases: 1. The activity is embedded in another app. Then the current organizer shouldn't control it. 2. The activity is in a TaskFragment that the organizer just request to remove, but hasn't reach the server side. Then the activity will soon be finished with the TaskFragment. In either case, the organizer shouldn't need to resolve it. Otherwise it may incorrectly change the state, such as entering split for a finishing activity. Bug: 233295443 Test: atest WMJetpackUnitTests:SplitControllerTest Change-Id: I5d2028dd45abd8d20a8e82bc4e51c4d6dc6e26ee
…
…
…
…
…
…
…
…
…
…
Merge "Remove unused empty filegroups from frameworks/base." am:
5ee9c55130 am: 76e9b955c5 am: 735d0192f6
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%