Skip to content

Commit

Permalink
cros: Fix login crash when determining if PIN is supported.
Browse files Browse the repository at this point in the history
Bug: 847040
Change-Id: Id32b31abdfa1dff8e8229bfb4eaa610d782d4789
Reviewed-on: https://chromium-review.googlesource.com/1077017
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562611}
  • Loading branch information
jacobdufault-google authored and Commit Bot committed May 29, 2018
1 parent 4b0d7de commit 4c830fc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion chrome/browser/chromeos/login/quick_unlock/pin_backend.cc
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,7 @@ bool PinBackend::ShouldUseCryptohome(const AccountId& account_id) {
// the prefs backend from a previous version. If that's the case, we should
// talk to the prefs backend instead of the cryptohome backend.
QuickUnlockStorage* storage = GetPrefsBackend(account_id);
return !storage->pin_storage_prefs()->IsPinSet();
return !storage || !storage->pin_storage_prefs()->IsPinSet();
}

} // namespace quick_unlock
Expand Down

0 comments on commit 4c830fc

Please sign in to comment.