RESTRICT AUTOMERGE:Make sure that the LockTaskUtilityActivityIfWhitelisted was started
Test:
run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceOwnerTest#testLockTaskAfterReboot_tryOpeningSettings_deviceOwnerUser
Root cause: When preparing to start LockTaskUtilityActivityIfWhitelisted, case starts android.settings.SETTINGS through the adb command first, resulting in LockTaskUtilityActivityIfWhitelisted not starting. We should wait for LockTaskUtilityActivityIfWhitelisted started to continue the following test.
Bug:147858236
Change-Id: I74a0c9b60e447f68733b77a2191e679eb62ba4c6
Merged-In: I6db66d7de561f031ccd79738224f2cd4b9a05e34
2 files changed