github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-11 09:06:13 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #4366] App logs me out if vault is unreachable #102132

New Issue
Closed
opened 2026-06-03 00:50:17 -05:00 by GiteaMirror · 21 comments
GiteaMirror commented 2026-06-03 00:50:17 -05:00
Owner
Copy Link

Originally created by @yurividal on GitHub (Nov 22, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4366

Steps To Reproduce

I self-host Bitwarden. Never had a problem with the old version of the android app. With the beta, I have realized that if my vault is unreachable, for example if my server went down for a few minutes, the Android app logs me out.
Next time I open the app, I have to log back in with my master password. Strangely, it doesn't request any 2FA for this re-login.
I also have to go to the settings and re-enable biometric login every time this happens.

Expected Result

Same behavior as old app. App keeps logged in even if vault is temporarily unavailable.

Actual Result

I have to login all over again.

Screenshots or Videos

No response

Additional Context

No response

Build Version

Latest

What server are you connecting to?

Self-host

Self-host Server Version

Latest

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 @yurividal on GitHub (Nov 22, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4366 ### Steps To Reproduce I self-host Bitwarden. Never had a problem with the old version of the android app. With the beta, I have realized that if my vault is unreachable, for example if my server went down for a few minutes, the Android app logs me out. Next time I open the app, I have to log back in with my master password. Strangely, it doesn't request any 2FA for this re-login. I also have to go to the settings and re-enable biometric login every time this happens. ### Expected Result Same behavior as old app. App keeps logged in even if vault is temporarily unavailable. ### Actual Result I have to login all over again. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version Latest ### What server are you connecting to? Self-host ### Self-host Server Version Latest ### Environment Details _No response_ ### 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-06-03 00:50:17 -05:00
GiteaMirror commented 2026-06-03 00:50:26 -05:00
Author
Owner
Copy Link

@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-15164

<!-- gh-comment-id:2492967994 --> @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-15164
GiteaMirror commented 2026-06-03 00:50:32 -05:00
Author
Owner
Copy Link

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

Steps to reproduce:

  • Open the beta android app
  • sync the vault. sync works fine.
  • go to reverse proxy and disable the bitwarden proxy (to simulate server being down)
  • open beta android app. wait for it to try to sync, or force a sync
  • exit out of the app
  • re-enable bitwarden on the reverse proxy
  • open the android app again. it will be logged out. User needs to enter master password again to log back in. All settings are also lost, so user needs to re-enable biometrics, and any other settings they had before.
<!-- gh-comment-id:2492990391 --> @yurividal commented on GitHub (Nov 22, 2024): Steps to reproduce: - Open the beta android app - sync the vault. sync works fine. - go to reverse proxy and disable the bitwarden proxy (to simulate server being down) - open beta android app. wait for it to try to sync, or force a sync - exit out of the app - re-enable bitwarden on the reverse proxy - open the android app again. it will be logged out. User needs to enter master password again to log back in. All settings are also lost, so user needs to re-enable biometrics, and any other settings they had before.
GiteaMirror commented 2026-06-03 00:50:39 -05:00
Author
Owner
Copy Link

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

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:2493338338 --> @daniellbw commented on GitHub (Nov 22, 2024): 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!
GiteaMirror commented 2026-06-03 00:50:45 -05:00
Author
Owner
Copy Link

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

Steps to reproduce:

  • Open the beta android app
  • sync the vault. sync works fine.
  • go to reverse proxy and disable the bitwarden proxy (to simulate server being down)
  • open beta android app. wait for it to try to sync, or force a sync
  • exit out of the app
  • re-enable bitwarden on the reverse proxy
  • open the android app again. it will be logged out. User needs to enter master password again to log back in. All settings are also lost, so user needs to re-enable biometrics, and any other settings they had before.

I sent this in via email but putting here as well:

Hi Android devs,

Big bug in version 2024.11.6
com.x8bit.bitwarden.

When internet is available but the self-hosted server is offline/unreachable/returning a 5xx, the app disregards prior biometric settings and logs me out.

That forces me to login, using my master password. That password is not accepted (an error occurred). It doesn't seem to use the local cached copy. I am logged out and unable to authenticate, locking me out entirely from my vault.

If I disable internet entirely, the app works as expected (AFTER returning the server to responding 2xx and logging in once, then setting biometrics again, and then disabling internet).

The issue is focused on when the server is unreachable OR returning a 5xx error. I've been locked out several times because of this due to an energy crisis in my country lasting beyond my UPS batteries >4hrs

<!-- gh-comment-id:2493428103 --> @ctrlbrk42 commented on GitHub (Nov 22, 2024): > Steps to reproduce: > > - Open the beta android app > - sync the vault. sync works fine. > - go to reverse proxy and disable the bitwarden proxy (to simulate server being down) > - open beta android app. wait for it to try to sync, or force a sync > - exit out of the app > - re-enable bitwarden on the reverse proxy > - open the android app again. it will be logged out. User needs to enter master password again to log back in. All settings are also lost, so user needs to re-enable biometrics, and any other settings they had before. > I sent this in via email but putting here as well: --- Hi Android devs, Big bug in version 2024.11.6 com.x8bit.bitwarden. When internet is available but the self-hosted server is offline/unreachable/returning a 5xx, the app disregards prior biometric settings and logs me out. That forces me to login, using my master password. That password is not accepted (an error occurred). It doesn't seem to use the local cached copy. I am logged out and unable to authenticate, locking me out entirely from my vault. If I disable internet entirely, the app works as expected (AFTER returning the server to responding 2xx and logging in once, then setting biometrics again, and then disabling internet). The issue is focused on when the server is unreachable OR returning a 5xx error. I've been locked out several times because of this due to an energy crisis in my country lasting beyond my UPS batteries >4hrs
GiteaMirror commented 2026-06-03 00:50:51 -05:00
Author
Owner
Copy Link

@ad-on-is commented on GitHub (Nov 23, 2024):

I have exactly the same issue.

I was wondering why the app keeps me asking for a master password randomly.

Wow! Given that my self-hosted server runs on a Ryzen mini PC, which is known to experience random restarts without any reason, this very much explains the problem.

<!-- gh-comment-id:2495538773 --> @ad-on-is commented on GitHub (Nov 23, 2024): I have exactly the same issue. I was wondering why the app keeps me asking for a master password randomly. Wow! Given that my self-hosted server runs on a Ryzen mini PC, which is known to experience random restarts without any reason, this very much explains the problem.
GiteaMirror commented 2026-06-03 00:50:54 -05:00
Author
Owner
Copy Link

@yurividal commented on GitHub (Nov 26, 2024):

Some users on Reddit are reporting this issue happens even on non-self-hosted.

<!-- gh-comment-id:2499554782 --> @yurividal commented on GitHub (Nov 26, 2024): [Some users on Reddit](https://www.reddit.com/r/Bitwarden/s/jTnnWrks4d) are reporting this issue happens even on non-self-hosted.
GiteaMirror commented 2026-06-03 00:50:58 -05:00
Author
Owner
Copy Link

@sorat0mo commented on GitHub (Nov 26, 2024):

I face the exact same issue. App randomly logs me out and sometimes vault appears empty for seconds.

<!-- gh-comment-id:2501187694 --> @sorat0mo commented on GitHub (Nov 26, 2024): I face the exact same issue. App randomly logs me out and sometimes vault appears empty for seconds.
GiteaMirror commented 2026-06-03 00:51:02 -05:00
Author
Owner
Copy Link

@fedonr commented on GitHub (Nov 27, 2024):

Same, I had 3 accounts on Biometric, it would unlock once with Biometric (when server is offline) but in few seconds it would throw error message (stays logged in). Close the from Recents and open it again, it'll be logged out. Same with all 3 accounts

<!-- gh-comment-id:2503017172 --> @fedonr commented on GitHub (Nov 27, 2024): Same, I had 3 accounts on Biometric, it would unlock once with Biometric (when server is offline) but in few seconds it would throw error message (stays logged in). Close the from Recents and open it again, it'll be logged out. Same with all 3 accounts
GiteaMirror commented 2026-06-03 00:51:06 -05:00
Author
Owner
Copy Link

@krasen1234 commented on GitHub (Dec 1, 2024):

Same issue only on Android, I changed proxy, host etc , keep having the issue

<!-- gh-comment-id:2509532189 --> @krasen1234 commented on GitHub (Dec 1, 2024): Same issue only on Android, I changed proxy, host etc , keep having the issue
GiteaMirror commented 2026-06-03 00:51:11 -05:00
Author
Owner
Copy Link

@Buenno commented on GitHub (Dec 4, 2024):

I'm also experiencing this issue. I'm running wireguard in order to access my self-hosted infra, but my work network blocks wireguard traffic. This causes my server to become unreachable, and my bitlocker account to disconnect.

<!-- gh-comment-id:2518510704 --> @Buenno commented on GitHub (Dec 4, 2024): I'm also experiencing this issue. I'm running wireguard in order to access my self-hosted infra, but my work network blocks wireguard traffic. This causes my server to become unreachable, and my bitlocker account to disconnect.
GiteaMirror commented 2026-06-03 00:51:18 -05:00
Author
Owner
Copy Link

@yurividal commented on GitHub (Dec 10, 2024):

Is this bug just going to keep being ignored by the Bitwarden team? So far, not even an acknowledgement from the developers...

<!-- gh-comment-id:2530052923 --> @yurividal commented on GitHub (Dec 10, 2024): Is this bug just going to keep being ignored by the Bitwarden team? So far, not even an acknowledgement from the developers...
GiteaMirror commented 2026-06-03 00:51:29 -05:00
Author
Owner
Copy Link

@krasen1234 commented on GitHub (Dec 10, 2024):

Works perfectly fine on other devices, I have 10 users and all problem with Android app

<!-- gh-comment-id:2530079664 --> @krasen1234 commented on GitHub (Dec 10, 2024): Works perfectly fine on other devices, I have 10 users and all problem with Android app
GiteaMirror commented 2026-06-03 00:51:35 -05:00
Author
Owner
Copy Link

@curtis-livefront commented on GitHub (Dec 11, 2024):

If you are still experiencing this issue, please share the following details.

  1. App Version: Which version of the app are you currently using?
  2. Log Out Behavior: Are you experiencing a soft logout (where some settings persist) or a hard logout (where all settings, including biometric login, are reset)?
  3. Confirm your environment: Are you experiencing this on Bitwarden.com or another environment?
<!-- gh-comment-id:2536219649 --> @curtis-livefront commented on GitHub (Dec 11, 2024): If you are still experiencing this issue, please share the following details. 1. App Version: Which version of the app are you currently using? 2. Log Out Behavior: Are you experiencing a soft logout (where some settings persist) or a hard logout (where all settings, including biometric login, are reset)? 3. Confirm your environment: Are you experiencing this on Bitwarden.com or another environment?
GiteaMirror commented 2026-06-03 00:51:36 -05:00
Author
Owner
Copy Link

@krasen1234 commented on GitHub (Dec 11, 2024):

If you are still experiencing this issue, please share the following details.

  1. App Version: Which version of the app are you currently using?
  2. Log Out Behavior: Are you experiencing a soft logout (where some settings persist) or a hard logout (where all settings, including biometric login, are reset)?
  3. Confirm your environment: Are you experiencing this on Bitwarden.com or another environment?
  1. All versions since the stupid UI and design change was done. Was fine before
  2. All is reset. Need to change the settings again
  3. Self hosted, tried several different proxys and even bare
<!-- gh-comment-id:2536278728 --> @krasen1234 commented on GitHub (Dec 11, 2024): > If you are still experiencing this issue, please share the following details. > > 1. App Version: Which version of the app are you currently using? > 2. Log Out Behavior: Are you experiencing a soft logout (where some settings persist) or a hard logout (where all settings, including biometric login, are reset)? > 3. Confirm your environment: Are you experiencing this on Bitwarden.com or another environment? 1. All versions since the stupid UI and design change was done. Was fine before 2. All is reset. Need to change the settings again 3. Self hosted, tried several different proxys and even bare
GiteaMirror commented 2026-06-03 00:51:37 -05:00
Author
Owner
Copy Link

@yurividal commented on GitHub (Dec 12, 2024):

Same here. Every version since thr UI refresh.
If I'm offline, or my self-histed vault is unreachable, even for a few minutes, the bitwarden app completely resets.
Logs me out, and resets all the settings.
I then have to login again. Strangely enough, it doesn't request 2FA when logging back in, so at least the session tokens are being saved.

<!-- gh-comment-id:2537610764 --> @yurividal commented on GitHub (Dec 12, 2024): Same here. Every version since thr UI refresh. If I'm offline, or my self-histed vault is unreachable, even for a few minutes, the bitwarden app completely resets. Logs me out, and resets all the settings. I then have to login again. Strangely enough, it doesn't request 2FA when logging back in, so at least the session tokens are being saved.
GiteaMirror commented 2026-06-03 00:51:37 -05:00
Author
Owner
Copy Link

@fedonr commented on GitHub (Dec 12, 2024):

Seems to be fixed in v2024.11.7, I tried the update and it doesn't log me out anymore, like it did earlier even when self-hosted instance is offline.

<!-- gh-comment-id:2540223989 --> @fedonr commented on GitHub (Dec 12, 2024): Seems to be fixed in v2024.11.7, I tried the update and it doesn't log me out anymore, like it did earlier even when self-hosted instance is offline.
GiteaMirror commented 2026-06-03 00:51:39 -05:00
Author
Owner
Copy Link

@curtis-livefront commented on GitHub (Dec 18, 2024):

@yurividal What is the latest version of the app that you are on?

<!-- gh-comment-id:2551612033 --> @curtis-livefront commented on GitHub (Dec 18, 2024): @yurividal What is the latest version of the app that you are on?
GiteaMirror commented 2026-06-03 00:51:40 -05:00
Author
Owner
Copy Link

@yurividal commented on GitHub (Dec 18, 2024):

Version: 2024.11.7 (19528)
It seems to have fixed this issue.

<!-- gh-comment-id:2551614788 --> @yurividal commented on GitHub (Dec 18, 2024): Version: 2024.11.7 (19528) It seems to have fixed this issue.
GiteaMirror commented 2026-06-03 00:51:41 -05:00
Author
Owner
Copy Link

@AE256orsomething commented on GitHub (Mar 15, 2025):

This is suddenly come back and has started happening to me recently using offical server and not self hosting.

  1. Android App Version: 2025.2.0 (19883)
  2. Hard logout where all settings and biometrics reset
  3. I am using offical app but unlock op I do NOT self host and use bitwarden.com

If you are still experiencing this issue, please share the following details.

1. App Version: Which version of the app are you currently using?

2. Log Out Behavior: Are you experiencing a soft logout (where some settings persist) or a hard logout (where all settings, including biometric login, are reset)?

3. Confirm your environment: Are you experiencing this on Bitwarden.com or another environment?
<!-- gh-comment-id:2726923215 --> @AE256orsomething commented on GitHub (Mar 15, 2025): This is suddenly come back and has started happening to me recently using offical server and not self hosting. 1. Android App Version: 2025.2.0 (19883) 2. Hard logout where all settings and biometrics reset 3. I am using offical app but unlock op I do NOT self host and use bitwarden.com > If you are still experiencing this issue, please share the following details. > > 1. App Version: Which version of the app are you currently using? > > 2. Log Out Behavior: Are you experiencing a soft logout (where some settings persist) or a hard logout (where all settings, including biometric login, are reset)? > > 3. Confirm your environment: Are you experiencing this on Bitwarden.com or another environment?
GiteaMirror commented 2026-06-03 00:51:42 -05:00
Author
Owner
Copy Link

@poly2it commented on GitHub (Oct 19, 2025):

I'm getting this issue multiple times daily, and it is really frustrating. We self-host Vaultwarden at my company. Can this issue be reopened?

<!-- gh-comment-id:3419932674 --> @poly2it commented on GitHub (Oct 19, 2025): I'm getting this issue multiple times daily, and it is really frustrating. We self-host Vaultwarden at my company. Can this issue be reopened?
GiteaMirror commented 2026-06-03 00:51:43 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 21, 2025):

@poly2it:

We self-host Vaultwarden at my company. Can this issue be reopened?

They explicitly request to raise any issues with them:

Image

(--> https://github.com/dani-garcia/vaultwarden)

<!-- gh-comment-id:3425470886 --> @pamperer562580892423 commented on GitHub (Oct 21, 2025): @poly2it: > We self-host Vaultwarden at my company. Can this issue be reopened? They explicitly request to raise any issues with them: <img width="854" height="150" alt="Image" src="https://github.com/user-attachments/assets/e6d94030-0bd7-4f50-9f18-8bb427eba7bf" /> (--> https://github.com/dani-garcia/vaultwarden)
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#102132
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?