-
Notifications
You must be signed in to change notification settings - Fork 842
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-15804, PM-17130: Add logic to monitor when the screen on state to ensure the vault locks properly #4618
PM-15804, PM-17130: Add logic to monitor when the screen on state to ensure the vault locks properly #4618
Conversation
… vault locks properly
New Issues (12)Checkmarx found the following issues in this Pull Request
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release/2025.01-rc14 #4618 +/- ##
========================================================
- Coverage 88.31% 88.31% -0.01%
========================================================
Files 603 603
Lines 40269 40291 +22
Branches 5697 5697
========================================================
+ Hits 35562 35581 +19
Misses 2721 2721
- Partials 1986 1989 +3 ☔ View full report in Codecov by Sentry. |
Thanks @phil-livefront & @dseverns-livefront |
🎟️ Tracking
PM-17130
PM-15804
📔 Objective
This PR adds a broadcast receiver to the
VaultLockManager
in order to ensure that we lock the vault at the soonest possible moment.There seems to be an issue in the way
delay
works inside a coroutine scope when the screen is off. Thedelay
will take significantly longer to complete and cause the vault to not lock when it is supposed to. This new solution restarts the delay with an appropriate remaining time when the screen is turned back on to ensure we lock the vault correctly.⏰ 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 confirmedissue 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