b48a4469ac
Currently, the changes to disable private space settings app component are located in SettiingsInitialize.java. These get triggered when ACTION_USER_INITIALIZE is received by the settings app inside the private profile user. However, we are stopping the private profile user at the end of the setup flow. This can lead to a scenario wherein ACTION_USER_INITIALIZE is relayed by the system server but not received by the private space settings app, since it was stopped. To over come this issue, we move the changes to disable the private space settings app component inside the private space setup flow (right after the user is created and started). Bug: 342165140 Test: atest PrivateSpaceMaintainerTest#createPrivateSpace_psDoesNotExist_setsPrivateSpaceSettingsComponentDisabled Flag: ACONFIG android.multiuser.enable_private_space_features NEXTFOOD Change-Id: Ib9baac1e9d835ea5a27c15d499e10615b84cf97b