github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 00:09:31 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #6760] [BWA-243] After reinstall the app existed 2FA keys still here #21759

New Issue
Open
opened 2026-04-16 22:22:46 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-16 22:22:46 -05:00
Owner
Copy Link

Originally created by @JerryIs-strong on GitHub (Apr 4, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6760

Steps To Reproduce

  1. ​Delete one of the 2FA keys
  2. Uninstall the Bitwarden Authenticator app
  3. Reinstall the app from the Google Play Store
  4. ​Open Bitwarden Authenticator; the deleted 5. 2FA keys is still there

Expected Result

All of the previously saved 2FA keys should have been removed

Actual Result

2FA account is still there

Screenshots or Videos

No response

Additional Context

After my test, I found that this bug just appears on my POCO phone running with stock rom but not on other devices.

Build Version

© Bitwarden Inc. 2015-2026 版本: 2026.3.1 (1478)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @JerryIs-strong on GitHub (Apr 4, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6760 ### Steps To Reproduce 1. ​Delete one of the 2FA keys 2. Uninstall the Bitwarden Authenticator app 3. Reinstall the app from the Google Play Store 4. ​Open Bitwarden Authenticator; the deleted 5. 2FA keys is still there ### Expected Result All of the previously saved 2FA keys should have been removed ### Actual Result 2FA account is still there ### Screenshots or Videos _No response_ ### Additional Context After my test, I found that this bug just appears on my POCO phone running with stock rom but not on other devices. ### Build Version © Bitwarden Inc. 2015-2026 版本: 2026.3.1 (1478) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details _No response_ ### Issue Tracking Info - [ ] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:authenticatorbug labels 2026-04-16 22:22:46 -05:00
GiteaMirror commented 2026-04-16 22:22:47 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Apr 4, 2026):

Thank you for your report! We've added this to our internal board for review.
ID: BWA-243

<!-- gh-comment-id:4187226354 --> @bitwarden-bot commented on GitHub (Apr 4, 2026): Thank you for your report! We've added this to our internal board for review. ID: [BWA-243](https://bitwarden.atlassian.net/browse/BWA-243) [BWA-243]: https://bitwarden.atlassian.net/browse/BWA-243?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-16 22:22:47 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 4, 2026):

Steps To Reproduce

  1. ​Delete one of the 2FA keys

Was that a local code in the authenticator app? Or was that a synced code in your authenticator app?

<!-- gh-comment-id:4187276578 --> @pamperer562580892423 commented on GitHub (Apr 4, 2026): > Steps To Reproduce > 1. ​Delete one of the 2FA keys Was that a **local code** in the authenticator app? Or was that a **synced code** in your authenticator app?
GiteaMirror commented 2026-04-16 22:22:47 -05:00
Author
Owner
Copy Link

@JerryIs-strong commented on GitHub (Apr 4, 2026):

Steps To Reproduce

  1. ​Delete one of the 2FA keys

Was that a local code in the authenticator app? Or was that a synced code in your authenticator app?

The local code

<!-- gh-comment-id:4187281749 --> @JerryIs-strong commented on GitHub (Apr 4, 2026): > > Steps To Reproduce > > > > 1. ​Delete one of the 2FA keys > > Was that a **local code** in the authenticator app? Or was that a **synced code** in your authenticator app? The **local code**
GiteaMirror commented 2026-04-16 22:22:48 -05:00
Author
Owner
Copy Link

@JerryIs-strong commented on GitHub (Apr 4, 2026):

Is this caused by the Android built-in backup system? Because on my phone running with lineage OS do not have this problem.

<!-- gh-comment-id:4187287939 --> @JerryIs-strong commented on GitHub (Apr 4, 2026): Is this caused by the Android built-in backup system? Because on my phone running with lineage OS do not have this problem.
GiteaMirror commented 2026-04-16 22:22:48 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 4, 2026):

Is this caused by the Android built-in backup system?

Did you wipe and restore your phone?

Actually, could you clarify on some other things?

Expected Result
All of the previously saved 2FA keys should have been removed

So, you expect all previously saved 2FA keys to have been removed? Also the not deleted ones or how do you mean that?

And your title is:

After reinstall the app existed 2FA keys still here

So, kind of "again": the 2FA keys that existed before the reinstall are the issue in general? Do you expect, after reinstall there should be no TOTP codes at all in the authenticator app? Please clarify the title.

<!-- gh-comment-id:4187295602 --> @pamperer562580892423 commented on GitHub (Apr 4, 2026): > Is this caused by the Android built-in backup system? Did you wipe and restore your phone? Actually, could you clarify on some other things? > Expected Result > All of the previously saved 2FA keys should have been removed So, you expect all previously saved 2FA keys to have been removed? Also the **not** deleted ones or how do you mean that? And your title is: > After reinstall the app existed 2FA keys still here So, kind of "again": the 2FA keys that existed before the reinstall are the issue in general? Do you expect, after reinstall there should be no TOTP codes at all in the authenticator app? Please clarify the title.
GiteaMirror commented 2026-04-16 22:22:49 -05:00
Author
Owner
Copy Link

@JerryIs-strong commented on GitHub (Apr 4, 2026):

I apologize for the confusion in my previous description. Let me clarify the situation in detail:

The Initial Discovery:
I originally had six 2FA keys stored locally in the Bitwarden Authenticator app. I uninstalled the app and then reinstalled it from the Google Play Store. To my surprise, all six 2FA keys were still there, even though the app had been removed.

The Persistent Data:
To fix this, I manually deleted each 2FA key one by one and cleared the app’s storage/cache. I then uninstalled the app and reinstalled it again from the Play Store. However, the same six 2FA keys reappeared once more.

<!-- gh-comment-id:4187307208 --> @JerryIs-strong commented on GitHub (Apr 4, 2026): I apologize for the confusion in my previous description. Let me clarify the situation in detail: The Initial Discovery: I originally had six 2FA keys stored locally in the Bitwarden Authenticator app. I uninstalled the app and then reinstalled it from the Google Play Store. To my surprise, all six 2FA keys were still there, even though the app had been removed. The Persistent Data: To fix this, I manually deleted each 2FA key one by one and cleared the app’s storage/cache. I then uninstalled the app and reinstalled it again from the Play Store. However, the same six 2FA keys reappeared once more.
GiteaMirror commented 2026-04-16 22:22:49 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 4, 2026):

Hm, @JerryIs-strong, honestly I wonder, if you would add a seventh TOTP code and didn't delete it, if that would be missing if you reinstalled. (in other words: if the "persistent data" of your authenticator app would be stuck now at the six TOTP codes, regardless of removing or adding other TOTP codes) 🤔

<!-- gh-comment-id:4187779470 --> @pamperer562580892423 commented on GitHub (Apr 4, 2026): Hm, @JerryIs-strong, honestly I wonder, if you would add a seventh TOTP code and didn't delete it, if that would be missing if you reinstalled. (in other words: if the "persistent data" of your authenticator app would be stuck now at the six TOTP codes, regardless of removing or adding other TOTP codes) 🤔
GiteaMirror commented 2026-04-16 22:22:49 -05:00
Author
Owner
Copy Link

@JerryIs-strong commented on GitHub (Apr 5, 2026):

I wonder, if you would add a seventh TOTP code and didn't delete it, if that would be missing if you reinstalled.

Hi~ @pamperer562580892423 I’ve just carried out a test, and as you might have expected, the seventh TOTP code has been lost, but the other six TOTP codes are still there.

<!-- gh-comment-id:4188093095 --> @JerryIs-strong commented on GitHub (Apr 5, 2026): > I wonder, if you would add a seventh TOTP code and didn't delete it, if that would be missing if you reinstalled. Hi~ @pamperer562580892423 I’ve just carried out a test, and as you might have expected, the seventh TOTP code has been lost, but the other six TOTP codes are still there.
GiteaMirror commented 2026-04-16 22:22:50 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Apr 6, 2026):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

<!-- gh-comment-id:4189923305 --> @rmcdowell-bitwarden commented on GitHub (Apr 6, 2026): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
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 app:authenticator bug
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#21759
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?