-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-13901] Bugfix for "Ask for biometrics on launch does not auto prompt biometrics" #12144
base: main
Are you sure you want to change the base?
[PM-13901] Bugfix for "Ask for biometrics on launch does not auto prompt biometrics" #12144
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #12144 +/- ##
==========================================
- Coverage 33.48% 33.48% -0.01%
==========================================
Files 2874 2875 +1
Lines 89821 89829 +8
Branches 17102 17102
==========================================
Hits 30075 30075
- Misses 57370 57378 +8
Partials 2376 2376 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
Fixed Issues
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-13901
📔 Objective
This PR ensures that, on the browser extension, biometrics gets auto-prompted when user selects "Ask for biometrics on launch" by resetting the
isInitialLockScreen
totrue
on active account change.The issue was that the
previousUrl
(see here) was maintaining a value , e.g. "/lockV2", which preventedunlockViaBiometrics()
from being run here. Therefore this PR resets theisInitialLockScreen
totrue
whenresetDataOnActiveAccountChange()
is run.Feature flag:
ExtensionRefresh
ON.📸 Screenshots
Chrome
chrome-auto-prompt.mov
Safari
safari-auto-prompt.mov
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes