github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-12 21:24:24 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Behaviour After Security Information Updates #281

New Issue
Closed
opened 2025-11-07 08:33:57 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-07 08:33:57 -06:00
Owner
Copy Link

Originally created by @Adam-Antios on GitHub (Sep 28, 2018).

I updated my security by adding two factor authentication to my account, but I had forgotten about it. So I was trying quite a while to find out why the app couldn't sync to my web vault. Moreover I realised that for a long time I was using an old version of my web vault as all the newest passwords were not synced.

The app itself didn't offer any warning that my information was updated so I could log in again from the app but it was working as usually, without of course having synced to the vault.

I don't think that this is the intended behaviour, is it? After the information gets updated I guess the app is supposed to alert the user or maybe log out, prompting him to log in again. At the very least a message should pop up that the security information has changed.

Originally created by @Adam-Antios on GitHub (Sep 28, 2018). I updated my security by adding two factor authentication to my account, but I had forgotten about it. So I was trying quite a while to find out why the app couldn't sync to my web vault. Moreover I realised that for a long time I was using an old version of my web vault as all the newest passwords were not synced. The app itself didn't offer any warning that my information was updated so I could log in again from the app but it was working as usually, without of course having synced to the vault. I don't think that this is the intended behaviour, is it? After the information gets updated I guess the app is supposed to alert the user or maybe log out, prompting him to log in again. At the very least a message should pop up that the security information has changed.
GiteaMirror commented 2025-11-07 08:33:58 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jun 4, 2019):

v2.0 has some improvements to log the user out on certain security events.

@kspearrin commented on GitHub (Jun 4, 2019): v2.0 has some improvements to log the user out on certain security events.
GiteaMirror commented 2025-11-07 08:33:58 -06:00
Author
Owner
Copy Link

@djsmith85 commented on GitHub (Mar 1, 2022):

Hi @Adam-Antios, it appears we've not heard from you about this issue in some time. While we are now closing this issue, if it continues to be a problem please feel free to re-open this issue and provide any further information that may be helpful in reproducing the problem or helping you further.

@djsmith85 commented on GitHub (Mar 1, 2022): Hi @Adam-Antios, it appears we've not heard from you about this issue in some time. While we are now closing this issue, if it continues to be a problem please feel free to re-open this issue and provide any further information that may be helpful in reproducing the problem or helping you further.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#281
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?