[GH-ISSUE #6882] Bitwarden regularly resets account Security and Other settings when Locked but not logged out. (the same happens after logging out and in) #102581

New Issue

2026-06-03T02:34:51-05:00

GiteaMirror commented

2026-06-03 02:34:51 -05:00

Originally created by @tdbe on GitHub (May 7, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6882

Steps To Reproduce

I used to suspect this happens after random bitwarden app updates, but as I detail below it seems more sinister.

I always set my account settings to: biometrics on, vault timeout 5m, clear clipboard 10s. They keep resetting every other week or every month. No other app on my device(s) has this issue.

Steps:

Your Bitwarden is logged in but Locked. Use your device as normally for a while. Get back to Bitwarden because you need some login for some website etc.

Open bitwarden, see that biometrics mysteriously turned off on the "Verify master password" screen (not a "log in" screen, but the Unlock screen). Write your password and unlock. Then go to your account Settings > Account Security > Unlock with Biometrics is now TURNED OFF. Session Timeout: is now set to 15 minutes.

Also go to Other settings: Clear clipboard is now reset to NEVER. -- May I suggest you have a "clear clipboard on lock" with ON by Default??? Most if not ALL open source password managers do this.

This is a huge SECURITY PROBLEM: Your user sets their account setting to clear clipboard to 10 seconds, and then a week later goes to the "Verify master password" screen, where it asks the password, the user maybe thinks "oh it must be that after a while it asks for password even if you have biometrics on", they then copy a login password, it Never clears, and hours later finds themselves accidentally pasting that password out of nowhere into a live field!? Dafuq, people?!

(I was not logged out, and even so it wouldn't explain the settings being reset inside my authenticated settings pages.)

(In my settings the session timeout action is always set to Lock (which is also the default setting).)

(The device's biometrics have NOT been changed, updated, been tampered with (other e.g. banking apps keep allowing biometrics - this doesn't happen after a biometrics change). And that would not explain all the other settings getting reset e.g. the session timeout and clipboard clear.)

To debug the issue, after re-setting my settings, I logged out (not lock, but log out this time) and then logged in again (with 2fa, the whole thing), and to my surprise, my account settings were also reset to defaults! Not just the biometrics while being logged out, but the ACCOUNT SETTINGS, the ones you can only see by being actively logged in and browsing your account, were reset. This cannot possibly be intended behaviour of a rational security app. Please tell me it's not. I kept waiting for this issue to be fixed for a long time, there have been other related issues that were "fixed".

Expected Result

When I set a damn setting, it should stay set. Even in the case that you overhaul the exact settings entry I have as non-default value, the correct protocol is to either keep my setting or warn me it was obsoleted. Still, in this case the issue repeats over many bitwarden versions and none of them had any visible changes to the Account Security page or the Other page.

Actual Result

See the "Steps to Reproduce" section. The account's settings get automagically RESET on you, randomly, with no warning, which leads to security breaches (e.g. someone pastes your password days later when you hand them your tablet)

Screenshots or Videos

No response

Additional Context

No response

Build Version

Bitwarden 2026.4.0 (21434)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

Device: Android 13, One UI 5.1.1 (was the same 1 or 2 versions ago)
Bitwarden version: 2026.4.0 (21434) (was the same every version in recent memory (years))

(from google play store)

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 @tdbe on GitHub (May 7, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6882 ### Steps To Reproduce I used to suspect this happens after random bitwarden app updates, but as I detail below it seems more sinister. I always set my account settings to: biometrics on, vault timeout 5m, clear clipboard 10s. They keep resetting every other week or every month. No other app on my device(s) has this issue. Steps: Your Bitwarden is logged in but Locked. Use your device as normally for a while. Get back to Bitwarden because you need some login for some website etc. Open bitwarden, see that biometrics mysteriously turned off on the "Verify master password" screen (not a "log in" screen, but the Unlock screen). Write your password and unlock. Then go to your account Settings > Account Security > `Unlock with Biometrics` is now TURNED OFF. `Session Timeout`: is now set to 15 minutes. Also go to Other settings: `Clear clipboard` is now reset to NEVER. -- May I suggest you have a "clear clipboard on lock" with ON by Default??? Most if not ALL open source password managers do this. This is a huge SECURITY PROBLEM: Your user sets their account setting to `clear clipboard` to 10 seconds, and then a week later goes to the "Verify master password" screen, where it asks the password, the user maybe thinks "oh it must be that after a while it asks for password even if you have biometrics on", they then copy a login password, it **Never** clears, and hours later finds themselves accidentally pasting that password out of nowhere into a live field!? Dafuq, people?! (I was not logged out, and even so it wouldn't explain the settings being reset inside my authenticated settings pages.) (In my settings the session timeout action is always set to Lock (which is also the default setting).) (The device's biometrics have NOT been changed, updated, been tampered with (other e.g. banking apps keep allowing biometrics - this doesn't happen after a biometrics change). And that would not explain all the other settings getting reset e.g. the session timeout and clipboard clear.) To debug the issue, after re-setting my settings, I logged out (not lock, but log out this time) and then logged in again (with 2fa, the whole thing), and to my surprise, my account settings were also reset to defaults! Not just the biometrics while being logged out, but the ACCOUNT SETTINGS, the ones you can only see by being actively logged in and browsing your account, were reset. This cannot possibly be intended behaviour of a rational security app. Please tell me it's not. I kept waiting for this issue to be fixed for a long time, there have been other related issues that were "fixed". ### Expected Result When I set a damn setting, it should stay set. Even in the case that you overhaul the exact settings entry I have as non-default value, the correct protocol is to either keep my setting or warn me it was obsoleted. Still, in this case the issue repeats over many bitwarden versions and none of them had any visible changes to the `Account Security` page or the `Other` page. ### Actual Result See the "Steps to Reproduce" section. The **account's** settings get automagically RESET on you, randomly, with no warning, which leads to security breaches (e.g. someone pastes your password days later when you hand them your tablet) ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version Bitwarden 2026.4.0 (21434) ### What server are you connecting to? EU ### Self-host Server Version _No response_ ### Environment Details - Device: Android 13, One UI 5.1.1 (was the same 1 or 2 versions ago) - Bitwarden version: 2026.4.0 (21434) (was the same every version in recent memory (years)) (from google play store) ### 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 app:password-manager labels 2026-06-03 02:34:51 -05:00

GiteaMirror closed this issue

2026-06-03 02:34:53 -05:00

GiteaMirror commented

2026-06-03 02:34:56 -05:00

@bitwarden-bot commented on GitHub (May 7, 2026):

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

@bitwarden-bot commented on GitHub (May 7, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-36850](https://bitwarden.atlassian.net/browse/PM-36850) [PM-36850]: https://bitwarden.atlassian.net/browse/PM-36850?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

GiteaMirror commented

2026-06-03 02:34:59 -05:00

@pamperer562580892423 commented on GitHub (May 7, 2026):

Another user here.

This is a huge SECURITY PROBLEM: I set clear clipboard to 10 seconds, and then a week later I log in with the password thinking

(emphasis my edit)

If you log out, it is expected that the vault data including settings get removed from your device. - As long as you just lock and unlock the BW app, your settings will be retained. See also: https://bitwarden.com/help/understand-log-in-vs-unlock/

@pamperer562580892423 commented on GitHub (May 7, 2026): Another user here. > This is a huge SECURITY PROBLEM: I set clear clipboard to 10 seconds, and then a week later **I log in** with the password thinking (emphasis my edit) If you log out, it is expected that the vault data including settings get removed from your device. - As long as you just **lock** and **unlock** the BW app, your settings will be retained. See also: https://bitwarden.com/help/understand-log-in-vs-unlock/

GiteaMirror commented

2026-06-03 02:35:02 -05:00

@tdbe commented on GitHub (May 7, 2026):

Oh, sorry I will fix my wording, it's not log in, it's authentication, ie entering the password only.

I never tap Log Out of bitwarden.
When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on.
Even if I was logging out, why the heck would the SETTINGS be reset? The settings can only be seen when you are authenticated ie also logged in, so there should be 0 cases when you see those settings in there reset.

@tdbe commented on GitHub (May 7, 2026): Oh, sorry I will fix my wording, it's not log in, it's authentication, ie entering the password only. - I never tap Log Out of bitwarden. - When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on. - Even if I was logging out, why the heck would the SETTINGS be reset? The settings can only be seen when you are authenticated ie also logged in, so there should be 0 cases when you see those settings in there reset.

GiteaMirror commented

2026-06-03 02:35:05 -05:00

@pamperer562580892423 commented on GitHub (May 7, 2026):

it's not log in, it's authentication, ie entering the password only.

So, you mean you unlock with master password? (there is either log in or unlock, so it's still a bit unclear what you mean with authentication)

I never tap Log Out of bitwarden.

Is your session timeout action set to "Lock" or "Log out":

?

If it's set to "Log out" then your app logs out automatically (instead of just locking).

When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on.

What exactly do you mean by "it's in the "Verify master password" screen"??

Even if I was logging out, why the heck would the SETTINGS be reset? The settings can only be seen when you are authenticated ie also logged in, so there should be 0 cases when you see those settings in there reset.

I can understand the desire to retain the settings also after logging out. - But on the other hand that is unrelated to the question if you "can see the settings" - or not.

@pamperer562580892423 commented on GitHub (May 7, 2026): > it's not log in, it's authentication, ie entering the password only. So, you mean you **unlock with master password**? (there is either **log in** or **unlock**, so it's still a bit unclear what you mean with _authentication_) > * I never tap Log Out of bitwarden. Is your session timeout action set to "Lock" or "Log out": <img width="496" height="224" alt="Image" src="https://github.com/user-attachments/assets/35e8658a-ef48-4207-9c28-ed587a14cc2f" /> ? If it's set to "Log out" then your app logs out automatically (instead of just locking). > * When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on. What exactly do you mean by "it's in the "Verify master password" screen"?? > * Even if I was logging out, why the heck would the SETTINGS be reset? The settings can only be seen when you are authenticated ie also logged in, so there should be 0 cases when you see those settings in there reset. I can understand the desire to retain the settings also after logging out. - But on the other hand that is unrelated to the question if you "can see the settings" - or not.

GiteaMirror commented

2026-06-03 02:35:09 -05:00

@tdbe commented on GitHub (May 7, 2026):

You sound like you're being purposefully obtuse. I've already provided enough redundant information, but okayI'll be extra pedantic one last time.

it's not log in, it's authentication, ie entering the password only.

So, you mean you unlock with master password? (there is either log in or unlock, so it's still a bit unclear what you mean with authentication)

I never tap Log Out of bitwarden.

I am NOT logged out. I am in this screen:

And sometimes it simply has the settings RESET. Ie no biometrics entry. I tried now to actually Log Out, and in that case the screen has a different title, says "log in" instead of "unlock", requires 2fa, etc.

Is your session timeout action set to "Lock" or "Log out":
?
If it's set to "Log out" then your app logs out automatically (instead of just locking).

I am not logged out, and also in my settings the session timeout action is set to Lock (which is also the default setting).

When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on.

What exactly do you mean by "it's in the "Verify master password" screen"??

I mean that screenshot mate, the one that all bitwarden users see when they Unlock their bitwarden! If your biometrics setting is reset to default in bitwarden (ie Off), it gets you the same screen, except without the unlock with biometrics button.

Even if I was logging out, why the heck would the SETTINGS be reset? The settings can only be seen when you are authenticated ie also logged in, so there should be 0 cases when you see those settings in there reset.

I can understand the desire to retain the settings also after logging out. - But on the other hand that is unrelated to the question if you "can see the settings" - or not.

I don't understand what you're not getting with this one. "I can understand the desire to retain the settings also after logging out" .... I am unlocked and I go to settings (which is the only way to see the settings - be actively logged in and unlocked) and inside those settings, I see the settings RESET! That is the problem. The settings, the account settings, are reset, even inside the settings page, the one you can only see when you're logged in and active and can copy passwords and shit. Even though I never logged out. And also after actually logging out and in again. Both cases are unacceptable, because they are account settings. But especially if you never logged out it is unacceptable.

@tdbe commented on GitHub (May 7, 2026): You sound like you're being purposefully obtuse. I've already provided enough redundant information, but okayI'll be extra pedantic one last time. > > it's not log in, it's authentication, ie entering the password only. > > So, you mean you **unlock with master password**? (there is either **log in** or **unlock**, so it's still a bit unclear what you mean with _authentication_) > > > * I never tap Log Out of bitwarden. I am NOT logged out. I am in this screen: <img width="1915" height="1080" alt="Image" src="https://github.com/user-attachments/assets/b61b76b7-5705-4d18-ab3d-79fd2328d95f" /> And sometimes it simply has the settings RESET. Ie no biometrics entry. I tried now to actually Log Out, and in that case the screen has a different title, says "log in" instead of "unlock", requires 2fa, etc. > Is your session timeout action set to "Lock" or "Log out": > > <img alt="Image" width="496" height="224" src="https://private-user-images.githubusercontent.com/138042245/589126984-35e8658a-ef48-4207-9c28-ed587a14cc2f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzgxODQ0NjUsIm5iZiI6MTc3ODE4NDE2NSwicGF0aCI6Ii8xMzgwNDIyNDUvNTg5MTI2OTg0LTM1ZTg2NThhLWVmNDgtNDIwNy05YzI4LWVkNTg3YTE0Y2MyZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNTA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDUwN1QyMDAyNDVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jMDU2OTRhNGVkZWU5NDI4MzcyYWJlMGRiNTdiNGRjZDY0YjNjMTNhZjBjNjBlODRhOTRlMTdlNTA4MzNmMGVjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.7G45xx8W5CDBAnzIkKvWyfMJPGL5YkK7SXqh3RBn_Ps"> > ? > > If it's set to "Log out" then your app logs out automatically (instead of just locking). I am not logged out, and also in my settings the `session timeout action` is set to Lock (which is also the default setting). > > * When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on. > > What exactly do you mean by "it's in the "Verify master password" screen"?? I mean that screenshot mate, the one that all bitwarden users see when they Unlock their bitwarden! If your biometrics setting is reset to default in bitwarden (ie Off), it gets you the same screen, except without the unlock with biometrics button. > > * Even if I was logging out, why the heck would the SETTINGS be reset? The settings can only be seen when you are authenticated ie also logged in, so there should be 0 cases when you see those settings in there reset. > > I can understand the desire to retain the settings also after logging out. - But on the other hand that is unrelated to the question if you "can see the settings" - or not. I don't understand what you're not getting with this one. "I can understand the desire to retain the settings also after logging out" .... I am unlocked and I go to settings (which is the only way to see the settings - be actively logged in and unlocked) and inside those settings, I see the settings RESET! That is the problem. The settings, the **account** settings, are reset, even inside the settings page, the one you can only see when you're logged in and active and can copy passwords and shit. Even though I never logged out. And also after actually logging out and in again. Both cases are unacceptable, because they are **account** settings. But especially if you never logged out it is unacceptable.

GiteaMirror commented

2026-06-03 02:35:11 -05:00

@pamperer562580892423 commented on GitHub (May 7, 2026):

When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on.

What exactly do you mean by "it's in the "Verify master password" screen"??

I mean that screenshot mate, the one that all bitwarden users see when they Unlock their bitwarden! If your biometrics setting is reset to default in bitwarden (ie Off), it gets you the same screen, except without the unlock with biometrics button.

Just to this part: Sorry, I didn't mean to irritate you. And I should have made the quote more explicit, as I indeed was confused by the whole expression "When the settings are reset, it's in the "Verify master password" screen". Thanks for clarifying.

@pamperer562580892423 commented on GitHub (May 7, 2026): > > > * When the settings are reset, it's in the "Verify master password" screen - the same screen that you can use Biometrics on when and if they're on. > > > > > > What exactly do you mean by "it's in the "Verify master password" screen"?? > > I mean that screenshot mate, the one that all bitwarden users see when they Unlock their bitwarden! If your biometrics setting is reset to default in bitwarden (ie Off), it gets you the same screen, except without the unlock with biometrics button. Just to this part: Sorry, I didn't mean to irritate you. And I should have made the quote more explicit, as I indeed was confused by the whole expression "When the settings are reset, it's in the "Verify master password" screen". Thanks for clarifying.

GiteaMirror commented

2026-06-03 02:35:14 -05:00

@tdbe commented on GitHub (May 7, 2026):

Ok no worries. We live in unprecedented internet (and global) climate 🙃 so that's why it's important for bitwarden to not bug out while you're in the middle of a long annoying stack of internet things.

@tdbe commented on GitHub (May 7, 2026): Ok no worries. We live in unprecedented internet (and global) climate 🙃 so that's why it's important for bitwarden to not bug out while you're in the middle of a long annoying stack of internet things.

GiteaMirror commented

2026-06-03 02:35:18 -05:00

@rmcdowell-bitwarden commented on GitHub (May 8, 2026):

Hi there,

I attempted to reproduce your issue and was unable to do so. I would recommend that you perform a clean reinstallation of your Bitwarden app using the steps below:

Uninstall the Bitwarden app
Restart the device (perform a full power cycle, shutting the device down completely and then restarting it)
Reinstall Bitwarden from the download link below

Bitwarden Downloads: https://bitwarden.com/download

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!

@rmcdowell-bitwarden commented on GitHub (May 8, 2026): Hi there, I attempted to reproduce your issue and was unable to do so. I would recommend that you perform a clean reinstallation of your Bitwarden app using the steps below: - Uninstall the Bitwarden app - Restart the device (perform a full power cycle, shutting the device down completely and then restarting it) - Reinstall Bitwarden from the download link below Bitwarden Downloads: https://bitwarden.com/download 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!

GiteaMirror commented

2026-06-03 02:35:20 -05:00

@tdbe commented on GitHub (May 8, 2026):

Hi there,

I attempted to reproduce your issue and was unable to do so. I would recommend that you perform a clean reinstallation of your Bitwarden app using the steps below:

Uninstall the Bitwarden app

Restart the device (perform a full power cycle, shutting the device down completely and then restarting it)

Reinstall Bitwarden from the download link below

Bitwarden Downloads: https://bitwarden.com/download

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!

It's a TIME BASED ISSUE, you disingenuous professional misconstruer: there are also lots of people in this other issue here with the same problem albeit more chaotically explained: https://github.com/bitwarden/android/issues/4650

Disingenuous twatness number 2: These steps objectively happen EVERY TIME on ALL DEVICES: Install Bitwarden on a new device, for example a Pixel 10. Log in. Set your settings. Then Log out. then Log in again. Your settings are all silently reset to defaults, your clipboard doesn't clear any more.

"Works for me insta-closed" good job bitwarden. Professional.

@tdbe commented on GitHub (May 8, 2026): > Hi there, > > I attempted to reproduce your issue and was unable to do so. I would recommend that you perform a clean reinstallation of your Bitwarden app using the steps below: > > * Uninstall the Bitwarden app > * Restart the device (perform a full power cycle, shutting the device down completely and then restarting it) > * Reinstall Bitwarden from the download link below > > Bitwarden Downloads: https://bitwarden.com/download > > 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! It's a TIME BASED ISSUE, you disingenuous professional misconstruer: there are also lots of people in this other issue here with the same problem albeit more chaotically explained: https://github.com/bitwarden/android/issues/4650 Disingenuous twatness number 2: These steps objectively happen EVERY TIME on ALL DEVICES: Install Bitwarden on a new device, for example a Pixel 10. Log in. Set your settings. Then Log out. then Log in again. Your settings are all silently reset to defaults, your clipboard doesn't clear any more. "Works for me insta-closed" good job bitwarden. Professional.

GiteaMirror commented

2026-06-03 02:35:25 -05:00

@SaintPatrck commented on GitHub (May 8, 2026):

@tdbe Could you turn on Flight recorder and leave it running until this behavior manifests again, and provide those logs either here or to our support team? That will give us more details we can use to investigate since we record logout reasons.

@SaintPatrck commented on GitHub (May 8, 2026): @tdbe Could you turn on Flight recorder and leave it running until this behavior manifests again, and provide those logs either here or to our support team? That will give us more details we can use to investigate since we record logout reasons.

GiteaMirror commented

2026-06-03 02:35:30 -05:00

@tdbe commented on GitHub (May 8, 2026):

I will try. I believe the issue might be related to Bitwarden's functionality of silently deleting settings, which gets triggered or doesn't get triggered on certain events. The events might be misbehaving. This "we silently delete your settings by design" functionality has 0 paths that aren't directly hurtful to the user, and 0 paths in which it is a security issue. As a matter of fact, deleting your security settings IS the security issue. The settings are part of your account + device id. they should always be applied when the account + device is present.

@tdbe commented on GitHub (May 8, 2026): I will try. I believe the issue might be related to Bitwarden's functionality of silently deleting settings, which gets triggered or doesn't get triggered on certain events. The events might be misbehaving. This "we silently delete your settings by design" functionality has 0 paths that aren't directly hurtful to the user, and 0 paths in which it is a security issue. As a matter of fact, deleting your security settings IS the security issue. The settings are part of your account + device id. they should always be applied when the account + device is present.

GiteaMirror commented

2026-06-03 02:35:37 -05:00

@tdbe commented on GitHub (May 27, 2026):

I got the problem again today. 3 weeks later. Flight recorder only lasts 1 week.

My version 3 weeks ago was:
Version: 2026.4.0 (21434)
📱 samsung SM-T97x 🤖 13@33 📦 prod
🧱 commit: https://github.com/bitwarden/android/commit/61955d7cbe1546a4c467284b4a5491d4f0e47afa
💻 build source: bitwarden/android/actions/runs/23952219208/attempts/1
🦀 SDK: 2.0.0-5676-14521973
🌩 Server: 2026.4.1 @ US

My version today is:
Version: 2026.4.2 (21562)
📱 samsung SM-T97x 🤖 13@33 📦 prod
🧱 commit: bitwarden/android/release/hotfix-v2026.4.1-bwpm@2e88a418a11a042fed230a0871cdcaa9bbff0c04
💻 build source: bitwarden/android/actions/runs/25866701011/attempts/1
🦀 SDK: 2.0.0-6825-release-hotfix-v2026.4.1-bwpm
🌩 Server: 2026.4.2 @ US

@tdbe commented on GitHub (May 27, 2026): I got the problem again today. 3 weeks later. Flight recorder only lasts 1 week. My version 3 weeks ago was: Version: 2026.4.0 (21434) 📱 samsung SM-T97x 🤖 13@33 📦 prod 🧱 commit: https://github.com/bitwarden/android/commit/61955d7cbe1546a4c467284b4a5491d4f0e47afa 💻 build source: bitwarden/android/actions/runs/23952219208/attempts/1 🦀 SDK: 2.0.0-5676-14521973 🌩 Server: 2026.4.1 @ US My version today is: Version: 2026.4.2 (21562) 📱 samsung SM-T97x 🤖 13@33 📦 prod 🧱 commit: bitwarden/android/release/hotfix-v2026.4.1-bwpm@2e88a418a11a042fed230a0871cdcaa9bbff0c04 💻 build source: bitwarden/android/actions/runs/25866701011/attempts/1 🦀 SDK: 2.0.0-6825-release-hotfix-v2026.4.1-bwpm 🌩 Server: 2026.4.2 @ US

Sign in to join this conversation.

Branches Tags

main

environment-update

PM-40631-display-personal-vault-as-my-vault

sdlc/sdk-update

renovate/lock-file-maintenance

PM-40527-send-controls-policy-data-model

cron-sync-privileged-browsers/70-sync

PM-40295-mp-policy-on-unlock

PM-40278-freeze-public-key

PM-40154-keystore-encrypted-shared-prefs

PM-39902-blob-encryption-support

worktree-QA-2177-blockeduri-testtag

PM-32685/test-support

cron-sync-privileged-browsers/69-sync

release/2026.7-rc58

PM-37256/merge-fill-assist-with-traverse

update-billing-api

agalles/create-deploy-workflow-trigger

llm/plan-implement-review-command

allow-user-certs

vvolkgang/fdroid-update

release/2026.6-rc57

agalles/create-github-workflow-trigger

release/2026.6-rc56

release/2026.5-rc55

release/2026.5-rc53

release/2026.5-rc54

PM-37255/consume-fill-assist-rules-data

PM-26896-autofill-fix

release/hotfix-v2026.4.1-bwpm

target-sdk-37

agalles/fdroid-only

BWA-99/show-next-totp

BWA-99/add-preview-next-totp-code-setting

sync-min-sdk

release/2026.4-rc51

related-origin-passkey-creation

release/2026.4-rc50

platform/android-breaking-change-detection

innovation-sprint-2026-send-folder

release/2026.3-rc49

PM-34193-vault-lockout

android-collections

llm/add-resolving-sdk-updates-skill

QA-1523/sanity-test-saucelabs

release/2026.3-rc48

release/2026.2-rc47

pr-6572

release/2026.2-rc46

release/2026.1-rc45

PM-30644/added-logs-for-debug

PM-30644/quicktile-nav-not-showing-migration

minor-gradle-updates

release/2026.1-rc42

release/2026.1-rc44

release/2026.1-rc43

PM-28834/set-landscape-on-horizonos-devices

PM-28468/validate-and-navigate-to-vault-migration

PM-20026/force-ltr-passwords-and-codes

release/2025.12-rc41

cmcg/testCoverage

PM-29014/talkback-support-for-passwords

release/2025.12-rc40

BRE-1305/publish_test

accept-user-certs

autofill-permissions

release/2025.11-rc39

PM-22479/check-all-certificates-validate-asset-links

release/2025.10-rc38

agalles/android-latest

retro-agent

PM-27001/skip-account-selection-only-one-exists-cxp

release/2025.10-rc37

agalles/test-1118

release/2025.10-rc36

PM-20593-token-refresh

QA-1126b/adding-native-sanity-test

release/2025.9-rc35

pm-25933/sdk-update-password

release/2025.9-rc34

release/2025.8-rc33

agalles/20250821-release

debug-release-issues

pm-24249-allow-automated-prs-for-sdk-updates

release/2025.8-rc32

release/WORKFLOW-TEST-2025.8-rc28

agalles/20250807release

release/2025.07-rc25

release/hotfix-v2025.7.0-bwa

pm-23311/export-vault-policy-bypass

release/2025.07-rc24

authenticator-pm-sync-flags-issue

release/hotfix-v2025.6.0-bwpm

release/2025.06-rc21

agalles/automate-android-fastlane-patch

release/2025.05-rc20

release/2025.04-rc19

languages/basque

release/2025.03-rc19

update-readme

qrcode/feature

innovation/archive/pm-19153-archive-items

qrcode/2-ui-fields

qrcode/1-page

hold-on-biometric-prompt-alternative

release-notes-process

release/2025.02-rc16

bwa-monorepo

PM-8223/new-device-verification-ux-improvements

pm-18451/exempt-from-policies

test-bwa

release/2025.01-rc15

release/2025.01-rc14

release/2024.12-rc13

pm-16670/sync-leave-notice

821

PM-16695/backport-lean-more-new-device-verification

release/hotfix-v2024.11.7

release/2024.11-rc1

pm-11304/collection-add-item-button

PM-14241/disabling-logs-app-crash

poc/offline-editing

new-version-calc

pm-11649/expired-link-services

pm-6702/add-feature-flag

pm-6702/email-verification-feature

pm-9933/marketing-copy-update

pm-6702/registration-flows

update-templates

pm-6701/email-verification-selfhost-registration

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/android#102581