Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f899bff7 authored by Robert Berry's avatar Robert Berry
Browse files

Add missing calls to key sync task in LockSettingsService 

On my device at least this was never getting called. Not sure if both
of these are needed.

Test: adb shell am instrument -w -e package com.android.server.locksettings.recoverablekeystore com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I693cf2f12a6d113b68dd4a8515aee97f4efb7b18
parent 4158a67a

services/core/java/com/android/server/locksettings/LockSettingsService.java

+5 −0
Original line number Diff line number Diff line
@@ -1581,6 +1581,8 @@ public class LockSettingsService extends ILockSettings.Stub { 
                userId, progressCallback);

        // The user employs synthetic password based credential.

        if (response != null) {

            mRecoverableKeyStoreManager.lockScreenSecretAvailable(credentialType, credential,

                    userId);

            return response;

        }
@@ -1705,6 +1707,9 @@ public class LockSettingsService extends ILockSettings.Stub { 
                                /* TODO(roosa): keep the same password quality */, userId);

                if (!hasChallenge) {

                    notifyActivePasswordMetricsAvailable(credential, userId);

                    // Use credentials to create recoverable keystore snapshot.

                    mRecoverableKeyStoreManager.lockScreenSecretAvailable(

                            storedHash.type, credential, userId);

                    return VerifyCredentialResponse.OK;

                }

                // Fall through to get the auth token. Technically this should never happen,