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

[BWA-82] Don't Timeout When User Selects Never #212

Merged

Conversation

brant-livefront
Copy link
Collaborator

@brant-livefront brant-livefront commented Dec 11, 2024

🎟️ Tracking

BWA-82

📔 Objective

This PR fixes an issue where a user who has biometric authentication turned on, but selects "Never" as their timeout duration would still be prompted for biometrics when the app was closed and re-opened. This PR adds an additional check on startup to allow the user to bypass biometric authentication if they have selected "Never".

📸 Screenshots

NeverLock.mp4

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 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

Copy link
Contributor

github-actions bot commented Dec 11, 2024

Logo
Checkmarx One – Scan Summary & Details07b7a544-5a74-4df2-b98e-6e348fc91b29

No New Or Fixed Issues Found

Copy link

codecov bot commented Dec 11, 2024

Codecov Report

Attention: Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Project coverage is 70.11%. Comparing base (d941bd1) to head (3652c6b).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...orShared/Core/Platform/Services/StateService.swift 0.00% 6 Missing ⚠️
...hared/UI/Platform/Application/AppCoordinator.swift 0.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #212      +/-   ##
==========================================
- Coverage   70.16%   70.11%   -0.06%     
==========================================
  Files         215      215              
  Lines        9865     9873       +8     
==========================================
  Hits         6922     6922              
- Misses       2943     2951       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -63,8 +63,12 @@ class AppCoordinator: Coordinator, HasRootNavigator {
func handleEvent(_ event: AppEvent, context: AnyObject?) async {
switch event {
case .didStart:
let accountId = await services.stateService.getActiveAccountId()
let hasTimeout = services.appSettingsStore.vaultTimeout(userId: accountId) !=
Copy link
Contributor

Choose a reason for hiding this comment

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

🤔 Could we get this setting from the state service as well? In PM, at least, we have convenience methods there that avoid needing to also get the account ID.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah that makes sense. It is awkward to have to do both.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Should be cleaned up a bit in the latest commit. 👍

@brant-livefront brant-livefront merged commit f124b31 into main Dec 12, 2024
7 checks passed
@brant-livefront brant-livefront deleted the brant/BWA-82-dont-timeout-when-user-selects-never branch December 12, 2024 22:03
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.

2 participants