github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-15 06:59:05 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Every version of Bitwarden beta starting with 2024.6.1-beta logs me out randomly (self hosted). #2021

New Issue
Closed
opened 2025-11-26 23:05:22 -06:00 by GiteaMirror · 35 comments
GiteaMirror commented 2025-11-26 23:05:22 -06:00
Owner
Copy Link

Originally created by @vinnyperella on GitHub (Oct 13, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Log in to self hosted instance.
  2. Open app after some time and it's already logged out or sometimes when I click an item in my Vault it logs me out.

Expected Result

Just as with the legacy .NET app I would expect it to stay logged in. I've tried multiple beta versions and all the results are the same.

Actual Result

I am logged out randomly and have to reenter my credentials and 2fa.

Screenshots or Videos

No response

Additional Context

I am using GrapheneOS (latest version) which has never been a problem with legacy apps.

Build Version

Currently: 2024.6.0 because it's the only one that doesn't exhibit this behavior but I've tried every beta.

Environment Details

Pixel 8 Pro, API level 34. GrapheneOS version 2024101200 kernel version 5.15.167-android14-11-gfe3eb0600ceb
#1 Fri Oct 11 02:03:20 UTC 2024

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 @vinnyperella on GitHub (Oct 13, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Log in to self hosted instance. 2. Open app after some time and it's already logged out or sometimes when I click an item in my Vault it logs me out. ### Expected Result Just as with the legacy .NET app I would expect it to stay logged in. I've tried multiple beta versions and all the results are the same. ### Actual Result I am logged out randomly and have to reenter my credentials and 2fa. ### Screenshots or Videos _No response_ ### Additional Context I am using GrapheneOS (latest version) which has never been a problem with legacy apps. ### Build Version Currently: 2024.6.0 because it's the only one that doesn't exhibit this behavior but I've tried every beta. ### Environment Details Pixel 8 Pro, API level 34. GrapheneOS version 2024101200 kernel version 5.15.167-android14-11-gfe3eb0600ceb #1 Fri Oct 11 02:03:20 UTC 2024 ### 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 app:password-managerbug labels 2025-11-26 23:05:22 -06:00
GiteaMirror commented 2025-11-26 23:05:23 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Oct 13, 2024):

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

@bitwarden-bot commented on GitHub (Oct 13, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-13500
GiteaMirror commented 2025-11-26 23:05:23 -06:00
Author
Owner
Copy Link

@sammbw commented on GitHub (Oct 14, 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!

@sammbw commented on GitHub (Oct 14, 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 2025-11-26 23:05:23 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 14, 2024):

@vinnyperella What is your server version?

@pamperer562580892423 commented on GitHub (Oct 14, 2024): @vinnyperella What is your server version?
GiteaMirror commented 2025-11-26 23:05:23 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Oct 14, 2024):

@vinnyperella What is your server version?

I'm using the latest version of self-hosted 2024.10.0 so my server version would be 2024.9.2.

Also wanted to mention I'm using the fdroid version.

@vinnyperella commented on GitHub (Oct 14, 2024): > @vinnyperella What is your server version? I'm using the latest version of self-hosted 2024.10.0 so my server version would be 2024.9.2. Also wanted to mention I'm using the fdroid version.
GiteaMirror commented 2025-11-26 23:05:23 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Oct 30, 2024):

I updated to latest self-hosted and this continues to happen. In GapheneOS you can view an apps system logs I grabbed them after it logged me out not sure if those would help. I was logged in then pressed the search button and it logged me out. It's getting to the point where I might revert back to 2024.6.0 the last release that worked.

I'll try 2024.10.1 and see if the same thing happens once it's released on F-Droid.

@vinnyperella commented on GitHub (Oct 30, 2024): I updated to latest self-hosted and this continues to happen. In GapheneOS you can view an apps system logs I grabbed them after it logged me out not sure if those would help. I was logged in then pressed the search button and it logged me out. It's getting to the point where I might revert back to 2024.6.0 the last release that worked. I'll try 2024.10.1 and see if the same thing happens once it's released on F-Droid.
GiteaMirror commented 2025-11-26 23:05:24 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Nov 1, 2024):

Same issue with 2024.10.2.

@vinnyperella commented on GitHub (Nov 1, 2024): Same issue with 2024.10.2.
GiteaMirror commented 2025-11-26 23:05:24 -06:00
Author
Owner
Copy Link

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

Facing the same issue. Also on GrapheneOS so that might have something to do with it. When I try to log in again I get an error telling me "We were unable to process your request" (Version: 2024.10.2)

@kedom1337 commented on GitHub (Nov 6, 2024): Facing the same issue. Also on GrapheneOS so that might have something to do with it. When I try to log in again I get an error telling me "We were unable to process your request" (Version: 2024.10.2)
GiteaMirror commented 2025-11-26 23:05:24 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Nov 13, 2024):

Same issue with 2024.11.3. The last version that didn't have this issue was 2024.6.0.

@vinnyperella commented on GitHub (Nov 13, 2024): Same issue with 2024.11.3. The last version that didn't have this issue was 2024.6.0.
GiteaMirror commented 2025-11-26 23:05:24 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Nov 13, 2024):

@vinnyperella Just out of curiousity: Did you try to delete the app data, delete the app, probably restart your phone and after that reinstall the app again? - And your server version is now on 2024.10.2 at the moment?

@pamperer562580892423 commented on GitHub (Nov 13, 2024): @vinnyperella Just out of curiousity: Did you try to delete the app data, delete the app, probably restart your phone and after that reinstall the app again? - And your server version is now on 2024.10.2 at the moment?
GiteaMirror commented 2025-11-26 23:05:24 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Nov 13, 2024):

@vinnyperella Just out of curiousity: Did you try to delete the app data, delete the app, probably restart your phone and after that reinstall the app again? - And your server version is now on 2024.10.2 at the moment?

I just performed those actions so we'll see but I do not have high hopes. And yes I am on the latest self-hosted version. This started occurring when you made the switch to the native version.

@vinnyperella commented on GitHub (Nov 13, 2024): > @vinnyperella Just out of curiousity: Did you try to delete the app data, delete the app, probably restart your phone and after that reinstall the app again? - And your server version is now on 2024.10.2 at the moment? I just performed those actions so we'll see but I do not have high hopes. And yes I am on the latest self-hosted version. This started occurring when you made the switch to the native version.
GiteaMirror commented 2025-11-26 23:05:25 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Nov 14, 2024):

I just performed those actions so we'll see but I do not have high hopes. And yes I am on the latest self-hosted version.

The first part: that is general troubleshooting - and it may be that in the data was some "hiccup" causing this. Or maybe not.

To the second part: I asked this, because it could also be an "interaction" between app and server (version), so I guess both should be reported.

This started occurring when you made the switch to the native version.

Sorry, I'm not from Bitwarden 😅 but just another user who stumbled upon this issue (while searching for another issue 😉 ) - and initially I noticed, that you didn't report the self-hosted server version... that's why I asked it initially.

I hope it get's resolved for you.

@pamperer562580892423 commented on GitHub (Nov 14, 2024): > I just performed those actions so we'll see but I do not have high hopes. And yes I am on the latest self-hosted version. The first part: that is general troubleshooting - and it may be that in the data was some "hiccup" causing this. Or maybe not. To the second part: I asked this, because it could also be an "interaction" between app and server (version), so I guess both should be reported. > This started occurring when you made the switch to the native version. Sorry, I'm not from Bitwarden 😅 but just another user who stumbled upon this issue (while searching for another issue 😉 ) - and initially I noticed, that you didn't report the self-hosted server version... that's why I asked it initially. I hope it get's resolved for you.
GiteaMirror commented 2025-11-26 23:05:25 -06:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Nov 16, 2024):

@sammbw @bitwarden-bot First of all, I'm using vaultwarden self-hosted server, so I'm not sharing this with request for support. Just sharing it with the hope that it might help you troubleshooting this as the issue might not be specific to any backend implementation.

Anyways, what I've noticed is that Bitwarden (this new Kotlin version) will log me out and forget all my settings when it tries to reach out to the server, but for some reason can't. I suppose this might be what hits folks here self hosting their servers - in case they are outside of their home network and don't have the service exposed publicly.

Steps to reproduce:

  1. Log into the account of self-hosted service that's only available within the local network
  2. Turn off wifi (but have mobile data on) or join different wifi where the server is not accesible
  3. Bitwarden kicks me out back to the initial log-in screen. There's no way to access the stored passwords.
  4. Even after connecting back to the previous wifi and server being accessible I have to log back in, all client settings are gone.

The old app handled this situation pretty transparently - some functionality didn't work (like saving new passwords) but otherwise passwords could be viewed locally without server being accessible. Unlocking with fingerprint worked, etc..

Apologies if this Vaultwarden-specific issue (doesn't look like) and hope it helps a bit.

@mprasil commented on GitHub (Nov 16, 2024): @sammbw @bitwarden-bot First of all, I'm using vaultwarden self-hosted server, so I'm not sharing this with request for support. Just sharing it with the hope that it _might_ help you troubleshooting this as the issue might not be specific to any backend implementation. Anyways, what I've noticed is that Bitwarden (this new Kotlin version) will log me out and forget all my settings when it tries to reach out to the server, but for some reason can't. I suppose this might be what hits folks here self hosting their servers - in case they are outside of their home network and don't have the service exposed publicly. Steps to reproduce: 1. Log into the account of self-hosted service that's only available within the local network 2. Turn off wifi (but have mobile data on) or join different wifi where the server is not accesible 3. Bitwarden kicks me out back to the initial log-in screen. There's no way to access the stored passwords. 4. Even after connecting back to the previous wifi and server being accessible I have to log back in, all client settings are gone. The old app handled this situation pretty transparently - some functionality didn't work (like saving new passwords) but otherwise passwords could be viewed locally without server being accessible. Unlocking with fingerprint worked, etc.. Apologies if this Vaultwarden-specific issue (doesn't look like) and hope it helps a bit.
GiteaMirror commented 2025-11-26 23:05:25 -06:00
Author
Owner
Copy Link

@danielgrant commented on GitHub (Nov 18, 2024):

Another +1 for this issue since upgrading to the native Android app (currently running 2024.11.5 on One UI 6.1 / Android 14) - this affects any self-hosted scenario (both self-hosting of the official server, and indeed Vaultwarden) where the app fails to connect to the backend after the vault is unlocked.

Instead of the legacy .NET app behaviour where one could still browse the vault and retrieve passwords, it simply logs them out. This is incredibly frustrating, as:

  1. Connectivity to the backend instance needs to be re-established to access the vault again; and
  2. It gets very tedious very quickly having to type in a 128 random character password several times a day.

This is quite simple to replicate as @mprasil has pointed out. There also another issue recently opened for this: https://github.com/bitwarden/android/issues/4318.

@danielgrant commented on GitHub (Nov 18, 2024): Another +1 for this issue since upgrading to the native Android app (currently running 2024.11.5 on One UI 6.1 / Android 14) - this affects any self-hosted scenario (both self-hosting of the official server, and indeed Vaultwarden) where the app fails to connect to the backend after the vault is unlocked. Instead of the legacy .NET app behaviour where one could still browse the vault and retrieve passwords, it simply logs them out. This is incredibly frustrating, as: 1. Connectivity to the backend instance needs to be re-established to access the vault again; and 2. It gets very tedious very quickly having to type in a 128 random character password several times a day. This is quite simple to replicate as @mprasil has pointed out. There also another issue recently opened for this: https://github.com/bitwarden/android/issues/4318.
GiteaMirror commented 2025-11-26 23:05:25 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Nov 20, 2024):

I put my phone in airplane mode and was still able to open the app and access my vault. I've found no way too reproduce this issue it happens randomly for me. I've upgraded to the latest self hosted instance and am using the 2024.11.3 Android app.

I have no issues with the browser extensions in Chromium or Firefox.

@vinnyperella commented on GitHub (Nov 20, 2024): I put my phone in airplane mode and was still able to open the app and access my vault. I've found no way too reproduce this issue it happens randomly for me. I've upgraded to the latest self hosted instance and am using the 2024.11.3 Android app. I have no issues with the browser extensions in Chromium or Firefox.
GiteaMirror commented 2025-11-26 23:05:25 -06:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Nov 20, 2024):

@vinnyperella I think you still need to have internet access to reproduce it. It seems to handle offline situation okay, it's just when it's online and can't access the service when this triggers for me.

@mprasil commented on GitHub (Nov 20, 2024): @vinnyperella I think you still need to have internet access to reproduce it. It seems to handle offline situation okay, it's just when it's online _and_ can't access the service when this triggers for me.
GiteaMirror commented 2025-11-26 23:05:26 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 9, 2024):

@sammbw With the last versions of the new native app (sideloaded via GitHub), I do see random logouts now as well. It happened at least with the 2024.11.5 and now with the 2024.11.7 (I'm not sure, if I encountered it with the previous versions, like 2024.11.3 or below... I'm pretty sure, it didn't happen to me with the last version of the old Android app 2024.10.0)

I set biometric unlock with 5 minutes vault timeout. A few times it may work (to just unlock as it should be) - but then suddenly I'm completely logged out in the app and have to login again.

I'm not self-hosted (= cloud-default). Android 14 on Fairphone 5.

PS: I already checked other settings... The battery setting is set to "unrestricted", the app doesn't get "killed"...

@pamperer562580892423 commented on GitHub (Dec 9, 2024): @sammbw With the last versions of the new native app (sideloaded via GitHub), I do see random logouts now as well. It happened at least with the 2024.11.5 and now with the 2024.11.7 (I'm not sure, if I encountered it with the previous versions, like 2024.11.3 or below... I'm pretty sure, it didn't happen to me with the last version of the old Android app 2024.10.0) I set biometric unlock with 5 minutes vault timeout. A few times it may work (to just unlock as it should be) - but then suddenly I'm completely logged out in the app and have to login again. I'm **not** self-hosted (= cloud-default). Android 14 on Fairphone 5. PS: I already checked other settings... The battery setting is set to "unrestricted", the app doesn't get "killed"...
GiteaMirror commented 2025-11-26 23:05:26 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Dec 16, 2024):

I hadn't been logged out for some time on 2024.11.7 until I upgraded my Bitwarden self hosted instance and rebooted the server to apply updates. As soon as I did that but had everything running it logged me out of the Android native client.

@vinnyperella commented on GitHub (Dec 16, 2024): I hadn't been logged out for some time on 2024.11.7 until I upgraded my Bitwarden self hosted instance and rebooted the server to apply updates. As soon as I did that but had everything running it logged me out of the Android native client.
GiteaMirror commented 2025-11-26 23:05:26 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jan 9, 2025):

This may have been fixed in 2025.1.0 which was released yesterday. I installed 2024.12.0 (prior release) and ran in to the issue when I stopped my Bitwarden self-hosted instance to patch the host. After installing 2025.1.0 I updated my SSL cert, which required me to stop the docker containers, and it did not log me out this time. Once the self-host repo gets updated with the new server and web versions for 2025.1.0 I will test again and reboot my VM to see if the issue persists.

Edit: Never mind, just got booted out on 2025.1.0.

@vinnyperella commented on GitHub (Jan 9, 2025): This may have been fixed in 2025.1.0 which was released yesterday. I installed 2024.12.0 (prior release) and ran in to the issue when I stopped my Bitwarden self-hosted instance to patch the host. After installing 2025.1.0 I updated my SSL cert, which required me to stop the docker containers, and it did not log me out this time. Once the self-host repo gets updated with the new server and web versions for 2025.1.0 I will test again and reboot my VM to see if the issue persists. Edit: Never mind, just got booted out on 2025.1.0.
GiteaMirror commented 2025-11-26 23:05:26 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jan 16, 2025):

Upgraded to self-host version 2025.1.0 (with Android version 2025.1.0 as well) and so far so good. Wasn't kicked out when I performed the upgrade which included a reboot of the server.

@vinnyperella commented on GitHub (Jan 16, 2025): Upgraded to self-host version 2025.1.0 (with Android version 2025.1.0 as well) and so far so good. Wasn't kicked out when I performed the upgrade which included a reboot of the server.
GiteaMirror commented 2025-11-26 23:05:27 -06:00
Author
Owner
Copy Link

@mprasil commented on GitHub (Jan 16, 2025):

@vinnyperella I think you're correct. With 2025.1.0 I can no longer reproduce the issue with my self-hosted instance.

@mprasil commented on GitHub (Jan 16, 2025): @vinnyperella I think you're correct. With 2025.1.0 I can no longer reproduce the issue with my self-hosted instance.
GiteaMirror commented 2025-11-26 23:05:27 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jan 18, 2025):

Bummer, just got booted out when I tried to search my vault.

@vinnyperella commented on GitHub (Jan 18, 2025): Bummer, just got booted out when I tried to search my vault.
GiteaMirror commented 2025-11-26 23:05:27 -06:00
Author
Owner
Copy Link

@jtruland commented on GitHub (Feb 26, 2025):

This seemed to be improved under 2025.1.x, but is now back with 2025.2.0 yesterday.

@jtruland commented on GitHub (Feb 26, 2025): This seemed to be improved under 2025.1.x, but is now back with 2025.2.0 yesterday.
GiteaMirror commented 2025-11-26 23:05:28 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Feb 26, 2025):

This seemed to be improved under 2025.1.x, but is now back with 2025.2.0 yesterday.

I only update when releases are posted on Github so I'm still on 2025.1.2 but I'm still experiencing the issue as you say albeit less often.

Edit: Oh, I see what you're saying, the self-host release 2025.2.0.

Still seeing the issue with:

self-host 2025.2.0
android 2025.1.2

@vinnyperella commented on GitHub (Feb 26, 2025): > This seemed to be improved under 2025.1.x, but is now back with 2025.2.0 yesterday. I only update when releases are posted on Github so I'm still on 2025.1.2 but I'm still experiencing the issue as you say albeit less often. Edit: Oh, I see what you're saying, the self-host release 2025.2.0. Still seeing the issue with: self-host 2025.2.0 android 2025.1.2
GiteaMirror commented 2025-11-26 23:05:28 -06:00
Author
Owner
Copy Link

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

I haven't been logged out yet on self host 2025.2.1 and Android 2025.2.0.

@vinnyperella commented on GitHub (Mar 15, 2025): I haven't been logged out yet on self host 2025.2.1 and Android 2025.2.0.
GiteaMirror commented 2025-11-26 23:05:28 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Mar 16, 2025):

Of course as soon as I make a comment after over a week of having no issues I get logged out...

@vinnyperella commented on GitHub (Mar 16, 2025): Of course as soon as I make a comment after over a week of having no issues I get logged out...
GiteaMirror commented 2025-11-26 23:05:28 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (May 7, 2025):

Still occuring on latest self-host (2025.4.2) and Android (2025.4.0) versions. This only seems to occur when the self-hosted instance is restarted however this is not an issue for the browser extensions. When I upgrade my self-hosted instance I always reboot my VPS and then when I go to use the Android app when it tries to sync is kicks me out to the login screen. I have not been logged out without restarting my self hosted instance in a very long time.

@vinnyperella commented on GitHub (May 7, 2025): Still occuring on latest self-host (2025.4.2) and Android (2025.4.0) versions. This only seems to occur when the self-hosted instance is restarted however this **is not** an issue for the browser extensions. When I upgrade my self-hosted instance I always reboot my VPS and then when I go to use the Android app when it tries to sync is kicks me out to the login screen. I have not been logged out without restarting my self hosted instance in a very long time.
GiteaMirror commented 2025-11-26 23:05:29 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (May 29, 2025):

This is still occuring on the latest self-host and Android version.

@vinnyperella commented on GitHub (May 29, 2025): This is still occuring on the latest self-host and Android version.
GiteaMirror commented 2025-11-26 23:05:29 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jun 12, 2025):

This is incredibly bad with the latest self-host (2025.5.2) and Android (2025.5.0) version I get logged out at least once per day.

@vinnyperella commented on GitHub (Jun 12, 2025): This is incredibly bad with the latest self-host (2025.5.2) and Android (2025.5.0) version I get logged out at least once per day.
GiteaMirror commented 2025-11-26 23:05:29 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jun 30, 2025):

Updated to Android version 2025.6.0 and have not been logged out yet. I even upgraded Bitwarden self-host to 2025.6.2 and reboot my VPS for patches, which usually triggers the logout scenario, and it has not occurred yet. 🤞🏼

@vinnyperella commented on GitHub (Jun 30, 2025): Updated to Android version 2025.6.0 and have not been logged out yet. I even upgraded Bitwarden self-host to 2025.6.2 and reboot my VPS for patches, which usually triggers the logout scenario, and it has not occurred yet. 🤞🏼
GiteaMirror commented 2025-11-26 23:05:29 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Jul 9, 2025):

Unfortunately the issue has come back with 2025.6.1 I get logged out at least once per day now.

@vinnyperella commented on GitHub (Jul 9, 2025): Unfortunately the issue has come back with 2025.6.1 I get logged out at least once per day now.
GiteaMirror commented 2025-11-26 23:05:30 -06:00
Author
Owner
Copy Link

@kedom1337 commented on GitHub (Jul 9, 2025):

Yeah same here. I again can't even log in

@kedom1337 commented on GitHub (Jul 9, 2025): Yeah same here. I again can't even log in
GiteaMirror commented 2025-11-26 23:05:30 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Aug 10, 2025):

Still an issue on 2025.7.2 basically every time I don't open the app for a while it opens but then if I do anything like search or open an item it logs me out. It's especially annoying because I don't carry my yubikey around which I need to log back in.

@vinnyperella commented on GitHub (Aug 10, 2025): Still an issue on 2025.7.2 basically every time I don't open the app for a while it opens but then if I do anything like search or open an item it logs me out. It's especially annoying because I don't carry my yubikey around which I need to log back in.
GiteaMirror commented 2025-11-26 23:05:30 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Sep 2, 2025):

This could potentially be fixed in 2025.8.0 I have not been logged out yet and I've upgraded my self host instance (including rebooting the host) and also reboot my phone a couple times.

@vinnyperella commented on GitHub (Sep 2, 2025): This could potentially be fixed in 2025.8.0 I have not been logged out yet and I've upgraded my self host instance (including rebooting the host) and also reboot my phone a couple times.
GiteaMirror commented 2025-11-26 23:05:30 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Sep 10, 2025):

Upgraded to Android 2025.8.1 and self-host 2025.8.3 and still have not been logged out I've even upgraded my self-host instance a couple times which generally causes the logout issue and it has been fine. Going to give it another week or so then close the issue if it doesn't return.

@vinnyperella commented on GitHub (Sep 10, 2025): Upgraded to Android 2025.8.1 and self-host 2025.8.3 and still have not been logged out I've even upgraded my self-host instance a couple times which generally causes the logout issue and it has been fine. Going to give it another week or so then close the issue if it doesn't return.
GiteaMirror commented 2025-11-26 23:05:31 -06:00
Author
Owner
Copy Link

@vinnyperella commented on GitHub (Sep 19, 2025):

Still not an issue in 2025.9.0, closing issue unless it returns.

@vinnyperella commented on GitHub (Sep 19, 2025): Still not an issue in 2025.9.0, closing issue unless it returns.
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:password-manager 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#2021
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?