-
Notifications
You must be signed in to change notification settings - Fork 812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Every version of Bitwarden beta starting with 2024.6.1-beta logs me out randomly (self hosted). #4081
Comments
Thank you for your report! We've added this to our internal board for review. |
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! |
@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. |
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. |
Same issue with 2024.10.2. |
Bitwarden Beta
Steps To Reproduce
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
The text was updated successfully, but these errors were encountered: