511460474367c5658cba30a21232f614efe6924b
Due to issues with an Intent filter not being configured with a category. We needed to move to launching the confirmation activity via Component targeting Intent. Hopefully this can be addressed post IC. Manual Testing: Start by navigating in Settings to: Settings > System > Reset Options > Erase Then click on "Reset Phone." At this point the behavior depends on the state of GmsCore. With forthcoming GmsCore changes (and accompanying SettingsGoogle changes), the user will see a prompt telling them that they can confirm their credentials. Regardless of whether the user successfully confirms or hits back, they will end up in the MasterClearConfirm UX. As per the feature spec. Test: make RunSettingsRoboTests -j40 Bug: 6393703 Change-Id: Idca02bda1fa2e388d612bd2014e16e2b6665fe70
Description
No description provided
Languages
Java
89.8%
Kotlin
10.2%