3f4bbc3a41
The current configuration in the client activity could be updated via the other flow (from ViewRootImpl). So, it is possible that the client activity configuration is different from the last reported configuration that cached in the system. If the configuration changed again in that case, the ActivityConfigurationChangeItem could end up without reporting Activity#onConfigurationChanged if the differences between the new configuration and the current client activity configuration contains the configuration changes that the activity cannot handle. Update the activity current config only when reported, so the configuration differences can be correctly evaluated from the new configuration and the configuration last reported. Bug: 231312158 Bug: 236415038 Test: repro steps on the bug Test: atest ActivityThreadClientTest Test: atest OverlayHostTest Change-Id: I56a871fb30809f5f75f0007601a7629f9435e03a