github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-11 10:54:26 -05:00
Code Issues 1.1k Packages Projects Releases 124 Wiki Activity

[GH-ISSUE #382] Behaviour After Security Information Updates #19908

New Issue
Closed
opened 2026-04-16 19:38:12 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-16 19:38:12 -05:00
Owner
Copy Link

Originally created by @Adam-Antios on GitHub (Sep 28, 2018).
Original GitHub issue: https://github.com/bitwarden/android/issues/382

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). Original GitHub issue: https://github.com/bitwarden/android/issues/382 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 2026-04-16 19:38:13 -05: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.

<!-- gh-comment-id:498722922 --> @kspearrin commented on GitHub (Jun 4, 2019): v2.0 has some improvements to log the user out on certain security events.
GiteaMirror commented 2026-04-16 19:38:14 -05: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.

<!-- gh-comment-id:1055973084 --> @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#19908
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?