github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-07-11 08:24:08 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #4241] Android client does not retain settings after logout #27943

New Issue
Closed
opened 2026-04-18 11:39:41 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 11:39:41 -05:00
Owner
Copy Link

Originally created by @raidenii on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4241

Steps To Reproduce

  1. Go to settings and change some user setting, e.g., others->clear clipboard to 30s
  2. Click logout from 3-dot menu after vault is locked
  3. Log back into Bitwarden
  4. Check settings

Expected Result

The client settings should retain.

Actual Result

Client settings are reverted to default.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.11.1

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden latest

Environment Details

Pixel 7 Android 15

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 @raidenii on GitHub (Nov 6, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4241 ### Steps To Reproduce 1. Go to settings and change some user setting, e.g., others->clear clipboard to 30s 2. Click logout from 3-dot menu after vault is locked 3. Log back into Bitwarden 4. Check settings ### Expected Result The client settings should retain. ### Actual Result Client settings are reverted to default. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2024.11.1 ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden latest ### Environment Details Pixel 7 Android 15 ### 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 2026-04-18 11:39:41 -05:00
GiteaMirror commented 2026-04-18 11:39:43 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:2459896082 --> @bitwarden-bot commented on GitHub (Nov 6, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-14545
GiteaMirror commented 2026-04-18 11:39:44 -05:00
Author
Owner
Copy Link

@SaintPatrck commented on GitHub (Nov 6, 2024):

Hi @raidenii,

Thank you for reporting your issue. The behavior you're describing is expected. When a user logs out all of their device specific settings, like vault timeout, are cleared. If you lock your vault instead of logging out, your settings will be retained when the vault is unlocked.

<!-- gh-comment-id:2459944778 --> @SaintPatrck commented on GitHub (Nov 6, 2024): Hi @raidenii, Thank you for reporting your issue. The behavior you're describing is expected. When a user logs out all of their device specific settings, like vault timeout, are cleared. If you lock your vault instead of logging out, your settings will be retained when the vault is unlocked.
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 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#27943
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?