Update to version 2024.11.6 (19499) "lost" all vault data #2078

Closed
opened 2025-11-26 23:07:19 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @RickPJ on GitHub (Nov 22, 2024).

Steps To Reproduce

Update to version 2024.11.6 (19499) via Play Store

Expected Result

App should run correctly as before

Actual Result

All vaults were empty, both personal and shared organisation

Screenshots or Videos

No response

Additional Context

The only action that recovered the vault was to delete all app data via Android settings (effectively app re-install), and login again from scratch. After that it was back to normal.
I don't know if this was a random glitch on my device or if it's a general problem. If the latter, it will be a support nightmare!

Build Version

2024.11.6 (19499)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Fairphone 3+, AOS 11

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 @RickPJ on GitHub (Nov 22, 2024). ### Steps To Reproduce Update to version 2024.11.6 (19499) via Play Store ### Expected Result App should run correctly as before ### Actual Result All vaults were empty, both personal and shared organisation ### Screenshots or Videos _No response_ ### Additional Context The only action that recovered the vault was to delete all app data via Android settings (effectively app re-install), and login again from scratch. After that it was back to normal. I don't know if this was a random glitch on my device or if it's a general problem. If the latter, it will be a support nightmare! ### Build Version 2024.11.6 (19499) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Fairphone 3+, AOS 11 ### Issue Tracking Info - [X] 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 bug label 2025-11-26 23:07:19 -06:00
Author
Owner

@bitwarden-bot commented on GitHub (Nov 22, 2024):

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

@bitwarden-bot commented on GitHub (Nov 22, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15168
Author
Owner

@Neonwarden commented on GitHub (Nov 22, 2024):

Hi there,

I attempted to reproduce your issue and was unable to do so.

We use GitHub issues as a place to track bugs and other development-related issues. If your issue persists, please write us back using our “Contact Support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

@Neonwarden commented on GitHub (Nov 22, 2024): Hi there, I attempted to reproduce your issue and was unable to do so. We use GitHub issues as a place to track bugs and other development-related issues. If your issue persists, please write us back using our “Contact Support” form located on our Help Center (https://bitwarden.com/help/). You can include a link to this issue in the message content. Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/). The issue here will be closed. Thanks!
Author
Owner

@Zoarial94 commented on GitHub (Nov 22, 2024):

I also experienced this issue. I only discovered the issue this morning, and I am on 2024.11.6 from GitHub directly. I was able to resolve the issue by logging out and back in.

I'm guessing the issue occurred a few days ago, and I only noticed today. What is notable is that I only had a single login listed, and it was one that I added yesterday.

Syncing the vault did not delete all the accounts since I was able to log out and back in to recovee everything.

Edit: I'm running a Pixel 6 Pro. Graphene OS/Android 15.

@Zoarial94 commented on GitHub (Nov 22, 2024): I also experienced this issue. I only discovered the issue this morning, and I am on 2024.11.6 from GitHub directly. I was able to resolve the issue by logging out and back in. I'm guessing the issue occurred a few days ago, and I only noticed today. What is notable is that I only had a single login listed, and it was one that I added yesterday. Syncing the vault did not delete all the accounts since I was able to log out and back in to recovee everything. Edit: I'm running a Pixel 6 Pro. Graphene OS/Android 15.
Author
Owner

@Bazixv13 commented on GitHub (Nov 23, 2024):

Noticed the same issue syncing the vault from the app setting didn't solve the problem I had to log out and log back maybe this occured because of autofill in not sure but it happened after clicking the autofill bitwarden in keyboard
app version: 2024.11.6

@Bazixv13 commented on GitHub (Nov 23, 2024): Noticed the same issue syncing the vault from the app setting didn't solve the problem I had to log out and log back maybe this occured because of autofill in not sure but it happened after clicking the autofill bitwarden in keyboard app version: 2024.11.6
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2078