You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
Bug description
When clicking the little "i" at the top right on the lock screen view, it shows an alert with an option to reset the password, but there's no way for the user to cancel the operation other than relaunching the app.
To Reproduce
Steps to reproduce the behavior:
Open the app (or click the lock icon when already in the app)
Click the "i" icon at the top
Expected behavior
There should be an option to dismiss the alert and to not reset the password. I clicked on it because I was curious what it is. Maybe the "Reset password" option should also have the descructive attribute to make it red.
Is there a backup of the data stored when resetting the password? Because currently it's a bit easy to reset it and delete all data which is really bad when you store all logins within the app.
Screenshots
Device
Device: iPad Air 4th generation
OS: iOS 15.0 Beta (19A5337a)
App Version 1.0 Build 8
The text was updated successfully, but these errors were encountered:
Bug description
When clicking the little "i" at the top right on the lock screen view, it shows an alert with an option to reset the password, but there's no way for the user to cancel the operation other than relaunching the app.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should be an option to dismiss the alert and to not reset the password. I clicked on it because I was curious what it is. Maybe the "Reset password" option should also have the
descructive
attribute to make it red.Is there a backup of the data stored when resetting the password? Because currently it's a bit easy to reset it and delete all data which is really bad when you store all logins within the app.
Screenshots
Device
The text was updated successfully, but these errors were encountered: