Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mob][auth] local_auth upgrade & work around for new applock key #2752

Merged
merged 6 commits into from
Aug 20, 2024

Conversation

AmanRajSinghMourya
Copy link
Contributor

No description provided.

}

Future<void> setHasMigratedLockScreenChanges() async {
if (_preferences.getBool(keyHasMigratedLockScreenChanges) == null ||
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can change this to just if (_preferences.getBool(keyHasMigratedLockScreenChanges) == null.
I couldn't understand why we need to check getUsAppLockSet here.

Future<void> setHasMigratedLockScreenChanges() async {
if (_preferences.getBool(keyHasMigratedLockScreenChanges) == null ||
getIsAppLockSet() == false) {
await _preferences.setBool(keyHasMigratedLockScreenChanges, true);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this to the end. So that only after everything is done we set this.
Why: let's say isPinSet() throws an error, the migration never completes but we set the key to true.

@ashilkn ashilkn merged commit 73b7b2e into lockscreen_auth_fixes Aug 20, 2024
2 checks passed
@ashilkn ashilkn deleted the lockscreen_auth_fixes_2 branch August 20, 2024 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants