283da3bf5f
When user dismiss pip, WindowOrganizerController#applyChanges would first try to resize pinned task, this will cause the activity to do ensureActivityConfiguration and which could trigger configuration change or relaunch the client activity. However, the windowing mode was not change yet, so the windowing mode change would be scheduled in another configuration change to client. But since the windowing mode is not public, client will treat there is difference so skip that configuration. To ensure client receive windowing mode change, check it before check configuration difference. And in order to prevent the WindowState#reportResized send before ActivityRelaunchItem send to client, skip resize if we already know that activity is going to relaunch. Bug: 165051679 Test: atest ActivityLifecyclePipTests ActivityLifecycleSplitScreenTests ActivityLifecycleTopResumedStateTests PinnedStackTests SplitScreenTests ActivityLifecycleKeyguardTests Change-Id: I7b96bbcf1a71ff75751e14db44c03261862bc857