Must turn biometrics on and reset timeout every time app starts #2157

@daniellbw commented on GitHub (Feb 6, 2025):

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!

@daniellbw commented on GitHub (Feb 6, 2025): 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

@lfrancke commented on GitHub (Feb 6, 2025):

I am "affected" by this as well. I can try to explain but I appreciate that it's hard to replicate. I am also not 100% sure if this is the exact same issue.

Since the update to the new version the App seems to have "forgotten" biometrics a few times. I can't see a pattern yet and it seems to be random (for now). So I'd unlock using biometrics in the morning and then in the afternoon have to enter my master password again and the biomterics setting is turned off. But as I said: The exact timing and circumstances seem random fo far. I just tried it a bunch of times and it worked as expected.

Is there any information we can look at when it happens again?

@lfrancke commented on GitHub (Feb 6, 2025): I am "affected" by this as well. I can try to explain but I appreciate that it's hard to replicate. I am also not 100% sure if this is the exact same issue. Since the update to the new version the App seems to have "forgotten" biometrics a few times. I can't see a pattern yet and it seems to be random (for now). So I'd unlock using biometrics in the morning and then in the afternoon have to enter my master password again and the biomterics setting is turned off. But as I said: The exact timing and circumstances seem random fo far. I just tried it a bunch of times and it worked as expected. Is there any information we can look at when it happens again?

GiteaMirror commented

@SaintPatrck commented on GitHub (Feb 6, 2025):

Hi all,

I'm not suggesting it's related to this issue, but we did identify an issue with biometrics when there are multiple accounts in use (#4683). As a result we've merge a fix (#4696) and added more descriptive error messaging. This will unfortunately require affected users to re-enable biometrics once again, but hopefully for the last time. 🤞

At the moment, enabling Crash logging in Settings is the best way for us to capture information on these types of issues. It's how we were ultimately able to track down the cause of #4683 and similar issues.

Once #4696 has been released please report back and let us know if you're still experiencing the issue.

@SaintPatrck commented on GitHub (Feb 6, 2025): Hi all, I'm not suggesting it's related to this issue, but we did identify an issue with biometrics when there are multiple accounts in use (#4683). As a result we've merge a fix (#4696) and added more descriptive error messaging. This will unfortunately require affected users to re-enable biometrics once again, but hopefully for the last time. 🤞 At the moment, enabling Crash logging in Settings is the best way for us to capture information on these types of issues. It's how we were ultimately able to track down the cause of #4683 and similar issues. Once #4696 has been released please report back and let us know if you're still experiencing the issue.

GiteaMirror commented

@felmey commented on GitHub (Feb 6, 2025):

Multiple accounts are not in use, but I will enable crash logging.

It happens so much now that in don't even enable biometrics much anymore as it is doesn't do anything at this point.

Sent from ProtonMail, encrypted email based in Switzerland.

Sent from Proton Mail Android

-------- Original Message --------
On 2/6/25 17:09, Patrick Honkonen wrote:

Hi all,

I'm not suggesting it's related to this issue, but we did identify an issue with biometrics when there are multiple accounts in use (#4683). As a result we've merge a fix (#4696) and added more descriptive error messaging. This will unfortunately require affected users to re-enable biometrics once again, but hopefully for the last time. 🤞

At the moment, enabling Crash logging in Settings is the best way for us to capture information on these types of issues. It's how we were ultimately able to track down the cause of #4683 and similar issues.

Once #4696 has been released please report back and let us know if you're still experiencing the issue.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@felmey commented on GitHub (Feb 6, 2025): Multiple accounts are not in use, but I will enable crash logging. It happens so much now that in don't even enable biometrics much anymore as it is doesn't do anything at this point. Sent from ProtonMail, encrypted email based in Switzerland. Sent from Proton Mail Android -------- Original Message -------- On 2/6/25 17:09, Patrick Honkonen wrote: > Hi all, > > I'm not suggesting it's related to this issue, but we did identify an issue with biometrics when there are multiple accounts in use ([#4683](https://github.com/bitwarden/android/issues/4683)). As a result we've merge a fix ([#4696](https://github.com/bitwarden/android/pull/4696)) and added more descriptive error messaging. This will unfortunately require affected users to re-enable biometrics once again, but hopefully for the last time. 🤞 > > At the moment, enabling Crash logging in Settings is the best way for us to capture information on these types of issues. It's how we were ultimately able to track down the cause of [#4683](https://github.com/bitwarden/android/issues/4683) and similar issues. > > Once [#4696](https://github.com/bitwarden/android/pull/4696) has been released please report back and let us know if you're still experiencing the issue. > > — > Reply to this email directly, [view it on GitHub](https://github.com/bitwarden/android/issues/4650#issuecomment-2641170272), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AD5UHVA352X4COYHFUMS5JL2OPMSZAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBRGE3TAMRXGI). > You are receiving this because you authored the thread.Message ID: ***@***.***>

GiteaMirror commented

2025-11-26 23:10:09 -06:00

@LukeMondy commented on GitHub (Feb 9, 2025):

I also have this issue

@LukeMondy commented on GitHub (Feb 9, 2025): I also have this issue

GiteaMirror commented

@leow149 commented on GitHub (Feb 10, 2025):

I get the same issue on version 2025.1.1 on Android 15. Timeout behavior is set to "Lock", but every now and then, i get logged out and it disables biometric login. I don't use multiple accounts, just one.

@leow149 commented on GitHub (Feb 10, 2025): I get the same issue on version 2025.1.1 on Android 15. Timeout behavior is set to "Lock", but every now and then, i get logged out and it disables biometric login. I don't use multiple accounts, just one.

GiteaMirror commented

2025-11-26 23:10:09 -06:00

@bmgoau commented on GitHub (Feb 11, 2025):

Can confirm. 2025.1.1
Sometimes once a day or multiple times a day butwarden locks and BOTH the lock timeout and biometric settings are defaulted.
It is NOT just biometrics it's lock timeout as well.
Single account.

@bmgoau commented on GitHub (Feb 11, 2025): Can confirm. 2025.1.1 Sometimes once a day or multiple times a day butwarden locks and BOTH the lock timeout and biometric settings are defaulted. It is NOT just biometrics it's lock timeout as well. Single account.

GiteaMirror commented

2025-11-26 23:10:09 -06:00

@djpeck1 commented on GitHub (Feb 12, 2025):

I also have the same issue with the Bitwarden Android app.

My phone is a Pixel 7 Pro running Android 15
I am using the Bitwarden Android app version 2025.1.2
Self hosting Bitwarden Unified server version 2025.1.0-beta on Google Cloud (container optimized OS)

The app randomly signs me out during the day and requires master password to sign back in and regularly gives the "Error, try again" prompt and often requires 3 or 4 attempts to get signed back in. Once I am signed back in I find that the biometric login setting has been reset along with the lock timeout.

The one time that this issue appears regularly is when the phone has been left switched on and charging overnight. When I go to unlock the Bitwarden app with biometrics it will unlock and within a few seconds sign me out and reset the biometric and lock settings. However I've no idea what causes this. Maybe Android OS puts the app to sleep or cuts off the data connection.

@djpeck1 commented on GitHub (Feb 12, 2025): I also have the same issue with the Bitwarden Android app. My phone is a Pixel 7 Pro running Android 15 I am using the Bitwarden Android app version 2025.1.2 Self hosting Bitwarden Unified server version 2025.1.0-beta on Google Cloud (container optimized OS) The app randomly signs me out during the day and requires master password to sign back in and regularly gives the "Error, try again" prompt and often requires 3 or 4 attempts to get signed back in. Once I am signed back in I find that the biometric login setting has been reset along with the lock timeout. The one time that this issue appears regularly is when the phone has been left switched on and charging overnight. When I go to unlock the Bitwarden app with biometrics it will unlock and within a few seconds sign me out and reset the biometric and lock settings. However I've no idea what causes this. Maybe Android OS puts the app to sleep or cuts off the data connection.

GiteaMirror commented

@Br33ce commented on GitHub (Feb 17, 2025):

Same problem for me unfortunately.

@Br33ce commented on GitHub (Feb 17, 2025): Same problem for me unfortunately.

GiteaMirror commented

@felmey commented on GitHub (Feb 22, 2025):

This is still happening. I thought it went away for a day or so, but it came back. Asks for master password instead of biometrics, and it deselects biometrics in settings and resets the timeout to 15 minutes.

@felmey commented on GitHub (Feb 22, 2025): This is still happening. I thought it went away for a day or so, but it came back. Asks for master password instead of biometrics, and it deselects biometrics in settings and resets the timeout to 15 minutes.

GiteaMirror commented

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

Same issue. It seems that whenever the login session ends or errors the biometric login selection is lost/reset.

@jtruland commented on GitHub (Feb 26, 2025): Same issue. It seems that whenever the login session ends or errors the biometric login selection is lost/reset.

GiteaMirror commented

@felmey commented on GitHub (Mar 17, 2025):

I was able to grab these logs when Bitwarden asked for biometrics, then dumped everything and asked for a login and password, and it reset the biometrics enabled to disabled and the timeout to default.

type: logcat
osVersion: google/cheetah/cheetah:15/BP1A.250305.019/2025031400:user/release-keys
flags: dev options enabled
package: com.x8bit.bitwarden:19883, targetSdk 35
buffers: main,system,crash,events,kernel
level: verbose

--------- beginning of events
03-16 23:00:39.465 29832 29832 I sqlite_mem_released: Memory released=0B
03-16 23:00:39.467 29832 29832 I force_gc: reason=mem
03-16 23:49:46.812 29832 29832 I sqlite_mem_released: Memory released=0B
03-16 23:49:46.813 29832 29832 I force_gc: reason=mem
--------- beginning of system
03-17 00:14:41.862 29832 29832 D ActivityThread: Package [dev.imranr.obtainium] reported as REPLACED, but missing application info. Assuming REMOVED.
03-17 00:14:41.875 29832 29832 D ActivityThread: Package [dev.imranr.obtainium] reported as REPLACED, but missing application info. Assuming REMOVED.
03-17 00:14:53.799 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider
03-17 00:14:53.800 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider
--------- beginning of main
03-17 00:14:53.833 29832 29832 I PendingIntentHandler: Request not found in pendingIntent
03-17 00:14:53.833 29832 29832 I PendingIntentHandler: Get request from framework is null
--------- switch to events
03-17 00:14:53.835 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=67ms]
03-17 00:14:53.836 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms]
--------- switch to system
03-17 00:14:53.837 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider
03-17 00:14:53.837 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider
--------- switch to events
03-17 00:14:53.838 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms]
03-17 00:14:53.848 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topStateChangedWhenResumed]
03-17 00:14:53.882 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=Canceling draw. cancelDueToPreDrawListener=true cancelDueToSync=false]
03-17 00:14:53.892 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=Draw frame after cancel]
03-17 00:14:53.895 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0]
--------- switch to main
03-17 00:14:53.977 29832 29832 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
03-17 00:14:53.977 29832 29832 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
03-17 00:14:53.992 29832 29832 D InsetsController: hide(ime(), fromIme=false)
03-17 00:14:53.992 29832 29832 I ImeTracker: com.x8bit.bitwarden:e769a76d: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN
03-17 00:14:56.187 29832 29832 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
03-17 00:14:56.187 29832 29832 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
03-17 00:14:56.233 29832 29832 D InsetsController: hide(ime(), fromIme=false)
03-17 00:14:56.233 29832 29832 I ImeTracker: com.x8bit.bitwarden:2c9a6f3: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN
03-17 00:14:56.304 29832 10330 W HWUI    : Image decoding logging dropped!
03-17 00:14:56.306 29832 10330 W HWUI    : Image decoding logging dropped!
03-17 00:14:56.307 29832 10330 W HWUI    : Image decoding logging dropped!
03-17 00:14:56.308 29832 10330 W HWUI    : Image decoding logging dropped!
03-17 00:14:56.474 29832 29876 I com.x8bit.bitwarden: Background concurrent mark compact GC freed 47MB AllocSpace bytes, 3(140KB) LOS objects, 75% free, 25MB/102MB, paused 4.761ms,1.030ms total 128.907ms
03-17 00:14:56.474 29832 29876 W com.x8bit.bitwarden: Reducing the number of considered missed Gc histogram windows from 151 to 100
03-17 00:14:56.717 29832  5621 W Glide   : Load failed for [https://bitwarden.redacted.org/icons/*.ual.com/icon.png] with dimensions [69x69]
03-17 00:14:56.717 29832  5621 W Glide   : class com.bumptech.glide.load.engine.GlideException: Failed to load resource
03-17 00:14:56.717 29832  5621 W Glide   : There was 1 root cause:
03-17 00:14:56.717 29832  5621 W Glide   : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400)
03-17 00:14:56.717 29832  5621 W Glide   :  call GlideException#logRootCauses(String) for more detail
03-17 00:14:56.717 29832  5621 W Glide   :   Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class java.io.InputStream, REMOTE
03-17 00:14:56.717 29832  5621 W Glide   : There was 1 root cause:
03-17 00:14:56.717 29832  5621 W Glide   : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400)
03-17 00:14:56.717 29832  5621 W Glide   :  call GlideException#logRootCauses(String) for more detail
03-17 00:14:56.717 29832  5621 W Glide   :     Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetch failed
03-17 00:14:56.717 29832  5621 W Glide   : There was 1 root cause:
03-17 00:14:56.717 29832  5621 W Glide   : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400)
03-17 00:14:56.717 29832  5621 W Glide   :  call GlideException#logRootCauses(String) for more detail
03-17 00:14:56.717 29832  5621 W Glide   :       Cause (1 of 1): class com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400
03-17 00:14:56.723 29832  5621 I Glide   : Root cause (1 of 1)
03-17 00:14:56.723 29832  5621 I Glide   : com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400
03-17 00:14:56.723 29832  5621 I Glide   : 	at com.bumptech.glide.load.data.l.d(Unknown Source:295)
03-17 00:14:56.723 29832  5621 I Glide   : 	at com.bumptech.glide.load.data.l.f(Unknown Source:25)
03-17 00:14:56.723 29832  5621 I Glide   : 	at n3.u.f(Unknown Source:24)
03-17 00:14:56.723 29832  5621 I Glide   : 	at j3.C.e(Unknown Source:141)
03-17 00:14:56.723 29832  5621 I Glide   : 	at j3.k.m(Unknown Source:25)
03-17 00:14:56.723 29832  5621 I Glide   : 	at j3.k.n(Unknown Source:45)
03-17 00:14:56.723 29832  5621 I Glide   : 	at j3.k.run(Unknown Source:23)
03-17 00:14:56.723 29832  5621 I Glide   : 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
03-17 00:14:56.723 29832  5621 I Glide   : 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
03-17 00:14:56.723 29832  5621 I Glide   : 	at I.i.run(Unknown Source:434)
03-17 00:14:56.723 29832  5621 I Glide   : 	at java.lang.Thread.run(Thread.java:1119)
03-17 00:14:56.723 29832  5621 I Glide   : 	at Zc.b.run(Unknown Source:10)
03-17 00:14:56.723 29832  5621 I Glide   : Caused by: java.io.FileNotFoundException: https://bitwarden.redacted.org/icons/*.ual.com/icon.png
03-17 00:14:56.723 29832  5621 I Glide   : 	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255)
03-17 00:14:56.723 29832  5621 I Glide   : 	at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211)
03-17 00:14:56.723 29832  5621 I Glide   : 	at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30)
03-17 00:14:56.723 29832  5621 I Glide   : 	at com.bumptech.glide.load.data.l.d(Unknown Source:98)
03-17 00:14:56.723 29832  5621 I Glide   : 	... 11 more
03-17 00:14:56.725 29832 29832 I ActivityThread: Schedule relaunch activity: com.x8bit.bitwarden.MainActivity
--------- switch to events
03-17 00:14:56.729 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=pausing]
03-17 00:14:56.729 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=0ms]
03-17 00:14:56.731 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleRelaunchActivity,time=0ms]
03-17 00:14:56.736 29832 29832 I wm_on_destroy_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performDestroy,time=0ms]
--------- switch to main
03-17 00:14:56.740 29832 29832 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=false callback=android.view.ViewRootImpl$$ExternalSyntheticLambda13@4e6ba39
--------- switch to system
03-17 00:14:56.746 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider
03-17 00:14:56.747 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider
--------- switch to events
03-17 00:14:56.748 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=8ms]
03-17 00:14:56.755 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms]
03-17 00:14:56.755 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms]
03-17 00:14:56.756 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topWhenResuming]
03-17 00:14:56.800 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0]
--------- switch to main
03-17 00:14:56.848 29832 10331 W Glide   : Load failed for [https://bitwarden.redacted.org/icons/*.ual.com/icon.png] with dimensions [69x69]
03-17 00:14:56.848 29832 10331 W Glide   : class com.bumptech.glide.load.engine.GlideException: Failed to load resource
03-17 00:14:56.848 29832 10331 W Glide   : There was 1 root cause:
03-17 00:14:56.848 29832 10331 W Glide   : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400)
03-17 00:14:56.848 29832 10331 W Glide   :  call GlideException#logRootCauses(String) for more detail
03-17 00:14:56.848 29832 10331 W Glide   :   Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class java.io.InputStream, REMOTE
03-17 00:14:56.848 29832 10331 W Glide   : There was 1 root cause:
03-17 00:14:56.848 29832 10331 W Glide   : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400)
03-17 00:14:56.848 29832 10331 W Glide   :  call GlideException#logRootCauses(String) for more detail
03-17 00:14:56.848 29832 10331 W Glide   :     Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetch failed
03-17 00:14:56.848 29832 10331 W Glide   : There was 1 root cause:
03-17 00:14:56.848 29832 10331 W Glide   : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400)
03-17 00:14:56.848 29832 10331 W Glide   :  call GlideException#logRootCauses(String) for more detail
03-17 00:14:56.848 29832 10331 W Glide   :       Cause (1 of 1): class com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400
03-17 00:14:56.848 29832 10331 I Glide   : Root cause (1 of 1)
03-17 00:14:56.848 29832 10331 I Glide   : com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400
03-17 00:14:56.848 29832 10331 I Glide   : 	at com.bumptech.glide.load.data.l.d(Unknown Source:295)
03-17 00:14:56.848 29832 10331 I Glide   : 	at com.bumptech.glide.load.data.l.f(Unknown Source:25)
03-17 00:14:56.848 29832 10331 I Glide   : 	at n3.u.f(Unknown Source:24)
03-17 00:14:56.848 29832 10331 I Glide   : 	at j3.C.e(Unknown Source:141)
03-17 00:14:56.848 29832 10331 I Glide   : 	at j3.k.m(Unknown Source:25)
03-17 00:14:56.848 29832 10331 I Glide   : 	at j3.k.n(Unknown Source:45)
03-17 00:14:56.848 29832 10331 I Glide   : 	at j3.k.run(Unknown Source:23)
03-17 00:14:56.848 29832 10331 I Glide   : 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
03-17 00:14:56.848 29832 10331 I Glide   : 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
03-17 00:14:56.848 29832 10331 I Glide   : 	at I.i.run(Unknown Source:434)
03-17 00:14:56.848 29832 10331 I Glide   : 	at java.lang.Thread.run(Thread.java:1119)
03-17 00:14:56.848 29832 10331 I Glide   : 	at Zc.b.run(Unknown Source:10)
03-17 00:14:56.848 29832 10331 I Glide   : Caused by: java.io.FileNotFoundException: https://bitwarden.redacted.org/icons/*.ual.com/icon.png
03-17 00:14:56.848 29832 10331 I Glide   : 	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255)
03-17 00:14:56.848 29832 10331 I Glide   : 	at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211)
03-17 00:14:56.848 29832 10331 I Glide   : 	at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30)
03-17 00:14:56.848 29832 10331 I Glide   : 	at com.bumptech.glide.load.data.l.d(Unknown Source:98)
03-17 00:14:56.848 29832 10331 I Glide   : 	... 11 more
03-17 00:14:56.969 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 47MB AllocSpace bytes, 2(72KB) LOS objects, 75% free, 18MB/74MB, paused 788us,1.151ms total 144.295ms
03-17 00:14:57.115 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 6100KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 13MB/54MB, paused 214us,585us total 44.299ms
03-17 00:14:57.356 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 148KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 13MB/54MB, paused 215us,539us total 40.239ms
03-17 00:14:57.699 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 2592KB AllocSpace bytes, 4(144KB) LOS objects, 75% free, 13MB/54MB, paused 755us,638us total 42.567ms
03-17 00:14:58.150 29832 29832 I ActivityThread: Schedule relaunch activity: com.x8bit.bitwarden.MainActivity
--------- switch to events
03-17 00:14:58.151 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=pausing]
03-17 00:14:58.153 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=0ms]
03-17 00:14:58.155 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleRelaunchActivity,time=0ms]
03-17 00:14:58.160 29832 29832 I wm_on_destroy_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performDestroy,time=0ms]
--------- switch to main
03-17 00:14:58.171 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 5900KB AllocSpace bytes, 4(208KB) LOS objects, 75% free, 9180KB/35MB, paused 510us,1.407ms total 70.395ms
--------- switch to system
03-17 00:14:58.179 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider
03-17 00:14:58.180 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider
--------- switch to events
03-17 00:14:58.182 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=17ms]
03-17 00:14:58.190 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms]
03-17 00:14:58.190 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms]
03-17 00:14:58.190 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topWhenResuming]
03-17 00:14:58.210 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0]
--------- switch to main
03-17 00:14:58.213 29832 29832 I ActivityThread: Schedule relaunch activity: com.x8bit.bitwarden.MainActivity
--------- switch to events
03-17 00:14:58.215 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=pausing]
03-17 00:14:58.215 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=1ms]
03-17 00:14:58.215 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleRelaunchActivity,time=0ms]
03-17 00:14:58.217 29832 29832 I wm_on_destroy_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performDestroy,time=0ms]
--------- switch to system
03-17 00:14:58.225 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider
03-17 00:14:58.225 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider
--------- switch to events
03-17 00:14:58.227 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=8ms]
03-17 00:14:58.233 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms]
03-17 00:14:58.234 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms]
03-17 00:14:58.234 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topWhenResuming]
03-17 00:14:58.249 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0]
--------- switch to main
03-17 00:14:58.379 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 1865KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 9927KB/38MB, paused 473us,1.282ms total 67.377ms
03-17 00:14:58.530 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 1226KB AllocSpace bytes, 1(16KB) LOS objects, 75% free, 8813KB/34MB, paused 337us,953us total 49.293ms
03-17 00:14:58.784 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 112KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 322us,962us total 51.671ms
03-17 00:14:59.147 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 422us,1.115ms total 60.619ms
03-17 00:14:59.599 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 319us,996us total 51.269ms
03-17 00:15:00.145 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8829KB/34MB, paused 320us,864us total 43.334ms
03-17 00:15:00.795 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 128KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 337us,863us total 48.662ms
03-17 00:15:01.543 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 320us,905us total 46.934ms
03-17 00:15:02.396 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 334us,943us total 50.578ms
03-17 00:15:03.342 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 120KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8837KB/34MB, paused 310us,954us total 44.999ms
03-17 00:15:03.394 29832 29832 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application.
03-17 00:15:03.394 29832 29832 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
--------- switch to events
03-17 00:15:03.436 29832 29832 I viewroot_draw_event: [window=VRI[Pop-Up Window],event=reportDrawFinished seqId=0]
--------- switch to main
03-17 00:15:03.451 29832 29832 D InsetsController: show(ime(), fromIme=false)
03-17 00:15:03.452 29832 29832 I ImeTracker: com.x8bit.bitwarden:3878917e: onRequestShow at ORIGIN_CLIENT reason SHOW_SOFT_INPUT_BY_INSETS_API fromUser false
--------- switch to system
03-17 00:15:03.453 29832 29832 D InsetsController: Setting requestedVisibleTypes to -1 (was -9)
--------- switch to main
03-17 00:15:03.460 29832 29832 I ImeTracker: com.x8bit.bitwarden:89450226: onRequestShow at ORIGIN_CLIENT reason SHOW_SOFT_INPUT fromUser false
03-17 00:15:03.460 29832 29832 D InsetsController: show(ime(), fromIme=false)
03-17 00:15:03.460 29832 29832 I ImeTracker: com.x8bit.bitwarden:89450226: onCancelled at PHASE_CLIENT_REPORT_REQUESTED_VISIBLE_TYPES
--------- switch to events
03-17 00:15:03.468 29832 10249 I viewroot_draw_event: [window=VRI[Pop-Up Window],event=reportDrawFinished seqId=0]
--------- switch to main
03-17 00:15:03.889 29832 29832 W InteractionJankMonitor: Initializing without READ_DEVICE_CONFIG permission. enabled=false, interval=1, missedFrameThreshold=3, frameTimeThreshold=64, package=com.x8bit.bitwarden
--------- switch to events
03-17 00:15:03.890 29832 27934 I jank_cuj_events_begin_request: [CUJ Type=80,Unix Time Ns=1742170503890053s,Elapsed Time Ns=103726589411.055s,Uptime Ns=76543122448.181s,Tag=0@1@com.x8bit.bitwarden]
--------- switch to main
03-17 00:15:03.948 29832 29832 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=false callback=android.view.ViewRootImpl$$ExternalSyntheticLambda13@29765f6
--------- switch to events
03-17 00:15:04.188 29832 27934 I jank_cuj_events_end_request: [CUJ Type=80,Unix Time Ns=1742170504188253s,Elapsed Time Ns=103726887611.617s,Uptime Time Ns=76543420648.661s]
--------- switch to main
03-17 00:15:04.188 29832 29832 I ImeTracker: com.x8bit.bitwarden:3878917e: onShown
--------- switch to events
03-17 00:15:13.784 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topStateChangedWhenResumed]
03-17 00:15:16.372 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=0ms]
--------- switch to main
03-17 00:15:16.759 29832 29832 D VRI[MainActivity]: visibilityChanged oldVisibility=true newVisibility=false
--------- switch to events
03-17 00:15:16.773 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=Not drawing due to not visible. Reason=!mAppVisible && !mForceDecorViewVisibility]
03-17 00:15:16.777 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=STOP_ACTIVITY_ITEM,time=2ms]
--------- switch to main
03-17 00:15:16.782 29832 29832 D InsetsController: hide(ime(), fromIme=false)
03-17 00:15:16.784 29832 29832 I ImeTracker: com.x8bit.bitwarden:63385b6e: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT_BY_INSETS_API fromUser false
03-17 00:15:16.784 29832 29832 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=false callback=android.view.ImeBackAnimationController@b1c47b4
--------- switch to system
03-17 00:15:16.784 29832 29832 D InsetsController: Setting requestedVisibleTypes to -9 (was -1)
--------- switch to events
03-17 00:15:16.786 29832 27934 I jank_cuj_events_begin_request: [CUJ Type=81,Unix Time Ns=1742170516786641s,Elapsed Time Ns=103739485999.603s,Uptime Ns=76556019036.81s,Tag=1@1@com.x8bit.bitwarden]
--------- switch to system
03-17 00:15:17.079 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider
03-17 00:15:17.080 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider
--------- switch to events
03-17 00:15:17.082 29832 27934 I jank_cuj_events_end_request: [CUJ Type=81,Unix Time Ns=1742170517082097s,Elapsed Time Ns=103739781458.465s,Uptime Time Ns=76556314495.795s]
--------- switch to main
03-17 00:15:17.093 29832 29832 W RemoteInputConnectionImpl: requestCursorUpdates on inactive InputConnection

@felmey commented on GitHub (Mar 17, 2025): I was able to grab these logs when Bitwarden asked for biometrics, then dumped everything and asked for a login and password, and it reset the biometrics enabled to disabled and the timeout to default. ``` type: logcat osVersion: google/cheetah/cheetah:15/BP1A.250305.019/2025031400:user/release-keys flags: dev options enabled package: com.x8bit.bitwarden:19883, targetSdk 35 buffers: main,system,crash,events,kernel level: verbose --------- beginning of events 03-16 23:00:39.465 29832 29832 I sqlite_mem_released: Memory released=0B 03-16 23:00:39.467 29832 29832 I force_gc: reason=mem 03-16 23:49:46.812 29832 29832 I sqlite_mem_released: Memory released=0B 03-16 23:49:46.813 29832 29832 I force_gc: reason=mem --------- beginning of system 03-17 00:14:41.862 29832 29832 D ActivityThread: Package [dev.imranr.obtainium] reported as REPLACED, but missing application info. Assuming REMOVED. 03-17 00:14:41.875 29832 29832 D ActivityThread: Package [dev.imranr.obtainium] reported as REPLACED, but missing application info. Assuming REMOVED. 03-17 00:14:53.799 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider 03-17 00:14:53.800 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider --------- beginning of main 03-17 00:14:53.833 29832 29832 I PendingIntentHandler: Request not found in pendingIntent 03-17 00:14:53.833 29832 29832 I PendingIntentHandler: Get request from framework is null --------- switch to events 03-17 00:14:53.835 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=67ms] 03-17 00:14:53.836 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms] --------- switch to system 03-17 00:14:53.837 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider 03-17 00:14:53.837 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider --------- switch to events 03-17 00:14:53.838 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms] 03-17 00:14:53.848 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topStateChangedWhenResumed] 03-17 00:14:53.882 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=Canceling draw. cancelDueToPreDrawListener=true cancelDueToSync=false] 03-17 00:14:53.892 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=Draw frame after cancel] 03-17 00:14:53.895 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0] --------- switch to main 03-17 00:14:53.977 29832 29832 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application. 03-17 00:14:53.977 29832 29832 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest. 03-17 00:14:53.992 29832 29832 D InsetsController: hide(ime(), fromIme=false) 03-17 00:14:53.992 29832 29832 I ImeTracker: com.x8bit.bitwarden:e769a76d: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN 03-17 00:14:56.187 29832 29832 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application. 03-17 00:14:56.187 29832 29832 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest. 03-17 00:14:56.233 29832 29832 D InsetsController: hide(ime(), fromIme=false) 03-17 00:14:56.233 29832 29832 I ImeTracker: com.x8bit.bitwarden:2c9a6f3: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN 03-17 00:14:56.304 29832 10330 W HWUI : Image decoding logging dropped! 03-17 00:14:56.306 29832 10330 W HWUI : Image decoding logging dropped! 03-17 00:14:56.307 29832 10330 W HWUI : Image decoding logging dropped! 03-17 00:14:56.308 29832 10330 W HWUI : Image decoding logging dropped! 03-17 00:14:56.474 29832 29876 I com.x8bit.bitwarden: Background concurrent mark compact GC freed 47MB AllocSpace bytes, 3(140KB) LOS objects, 75% free, 25MB/102MB, paused 4.761ms,1.030ms total 128.907ms 03-17 00:14:56.474 29832 29876 W com.x8bit.bitwarden: Reducing the number of considered missed Gc histogram windows from 151 to 100 03-17 00:14:56.717 29832 5621 W Glide : Load failed for [https://bitwarden.redacted.org/icons/*.ual.com/icon.png] with dimensions [69x69] 03-17 00:14:56.717 29832 5621 W Glide : class com.bumptech.glide.load.engine.GlideException: Failed to load resource 03-17 00:14:56.717 29832 5621 W Glide : There was 1 root cause: 03-17 00:14:56.717 29832 5621 W Glide : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400) 03-17 00:14:56.717 29832 5621 W Glide : call GlideException#logRootCauses(String) for more detail 03-17 00:14:56.717 29832 5621 W Glide : Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class java.io.InputStream, REMOTE 03-17 00:14:56.717 29832 5621 W Glide : There was 1 root cause: 03-17 00:14:56.717 29832 5621 W Glide : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400) 03-17 00:14:56.717 29832 5621 W Glide : call GlideException#logRootCauses(String) for more detail 03-17 00:14:56.717 29832 5621 W Glide : Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetch failed 03-17 00:14:56.717 29832 5621 W Glide : There was 1 root cause: 03-17 00:14:56.717 29832 5621 W Glide : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400) 03-17 00:14:56.717 29832 5621 W Glide : call GlideException#logRootCauses(String) for more detail 03-17 00:14:56.717 29832 5621 W Glide : Cause (1 of 1): class com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400 03-17 00:14:56.723 29832 5621 I Glide : Root cause (1 of 1) 03-17 00:14:56.723 29832 5621 I Glide : com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400 03-17 00:14:56.723 29832 5621 I Glide : at com.bumptech.glide.load.data.l.d(Unknown Source:295) 03-17 00:14:56.723 29832 5621 I Glide : at com.bumptech.glide.load.data.l.f(Unknown Source:25) 03-17 00:14:56.723 29832 5621 I Glide : at n3.u.f(Unknown Source:24) 03-17 00:14:56.723 29832 5621 I Glide : at j3.C.e(Unknown Source:141) 03-17 00:14:56.723 29832 5621 I Glide : at j3.k.m(Unknown Source:25) 03-17 00:14:56.723 29832 5621 I Glide : at j3.k.n(Unknown Source:45) 03-17 00:14:56.723 29832 5621 I Glide : at j3.k.run(Unknown Source:23) 03-17 00:14:56.723 29832 5621 I Glide : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) 03-17 00:14:56.723 29832 5621 I Glide : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651) 03-17 00:14:56.723 29832 5621 I Glide : at I.i.run(Unknown Source:434) 03-17 00:14:56.723 29832 5621 I Glide : at java.lang.Thread.run(Thread.java:1119) 03-17 00:14:56.723 29832 5621 I Glide : at Zc.b.run(Unknown Source:10) 03-17 00:14:56.723 29832 5621 I Glide : Caused by: java.io.FileNotFoundException: https://bitwarden.redacted.org/icons/*.ual.com/icon.png 03-17 00:14:56.723 29832 5621 I Glide : at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255) 03-17 00:14:56.723 29832 5621 I Glide : at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211) 03-17 00:14:56.723 29832 5621 I Glide : at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30) 03-17 00:14:56.723 29832 5621 I Glide : at com.bumptech.glide.load.data.l.d(Unknown Source:98) 03-17 00:14:56.723 29832 5621 I Glide : ... 11 more 03-17 00:14:56.725 29832 29832 I ActivityThread: Schedule relaunch activity: com.x8bit.bitwarden.MainActivity --------- switch to events 03-17 00:14:56.729 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=pausing] 03-17 00:14:56.729 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=0ms] 03-17 00:14:56.731 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleRelaunchActivity,time=0ms] 03-17 00:14:56.736 29832 29832 I wm_on_destroy_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performDestroy,time=0ms] --------- switch to main 03-17 00:14:56.740 29832 29832 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=false callback=android.view.ViewRootImpl$$ExternalSyntheticLambda13@4e6ba39 --------- switch to system 03-17 00:14:56.746 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider 03-17 00:14:56.747 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider --------- switch to events 03-17 00:14:56.748 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=8ms] 03-17 00:14:56.755 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms] 03-17 00:14:56.755 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms] 03-17 00:14:56.756 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topWhenResuming] 03-17 00:14:56.800 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0] --------- switch to main 03-17 00:14:56.848 29832 10331 W Glide : Load failed for [https://bitwarden.redacted.org/icons/*.ual.com/icon.png] with dimensions [69x69] 03-17 00:14:56.848 29832 10331 W Glide : class com.bumptech.glide.load.engine.GlideException: Failed to load resource 03-17 00:14:56.848 29832 10331 W Glide : There was 1 root cause: 03-17 00:14:56.848 29832 10331 W Glide : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400) 03-17 00:14:56.848 29832 10331 W Glide : call GlideException#logRootCauses(String) for more detail 03-17 00:14:56.848 29832 10331 W Glide : Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class java.io.InputStream, REMOTE 03-17 00:14:56.848 29832 10331 W Glide : There was 1 root cause: 03-17 00:14:56.848 29832 10331 W Glide : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400) 03-17 00:14:56.848 29832 10331 W Glide : call GlideException#logRootCauses(String) for more detail 03-17 00:14:56.848 29832 10331 W Glide : Cause (1 of 1): class com.bumptech.glide.load.engine.GlideException: Fetch failed 03-17 00:14:56.848 29832 10331 W Glide : There was 1 root cause: 03-17 00:14:56.848 29832 10331 W Glide : com.bumptech.glide.load.HttpException(Failed to connect or obtain data, status code: 400) 03-17 00:14:56.848 29832 10331 W Glide : call GlideException#logRootCauses(String) for more detail 03-17 00:14:56.848 29832 10331 W Glide : Cause (1 of 1): class com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400 03-17 00:14:56.848 29832 10331 I Glide : Root cause (1 of 1) 03-17 00:14:56.848 29832 10331 I Glide : com.bumptech.glide.load.HttpException: Failed to connect or obtain data, status code: 400 03-17 00:14:56.848 29832 10331 I Glide : at com.bumptech.glide.load.data.l.d(Unknown Source:295) 03-17 00:14:56.848 29832 10331 I Glide : at com.bumptech.glide.load.data.l.f(Unknown Source:25) 03-17 00:14:56.848 29832 10331 I Glide : at n3.u.f(Unknown Source:24) 03-17 00:14:56.848 29832 10331 I Glide : at j3.C.e(Unknown Source:141) 03-17 00:14:56.848 29832 10331 I Glide : at j3.k.m(Unknown Source:25) 03-17 00:14:56.848 29832 10331 I Glide : at j3.k.n(Unknown Source:45) 03-17 00:14:56.848 29832 10331 I Glide : at j3.k.run(Unknown Source:23) 03-17 00:14:56.848 29832 10331 I Glide : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) 03-17 00:14:56.848 29832 10331 I Glide : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651) 03-17 00:14:56.848 29832 10331 I Glide : at I.i.run(Unknown Source:434) 03-17 00:14:56.848 29832 10331 I Glide : at java.lang.Thread.run(Thread.java:1119) 03-17 00:14:56.848 29832 10331 I Glide : at Zc.b.run(Unknown Source:10) 03-17 00:14:56.848 29832 10331 I Glide : Caused by: java.io.FileNotFoundException: https://bitwarden.redacted.org/icons/*.ual.com/icon.png 03-17 00:14:56.848 29832 10331 I Glide : at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255) 03-17 00:14:56.848 29832 10331 I Glide : at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211) 03-17 00:14:56.848 29832 10331 I Glide : at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30) 03-17 00:14:56.848 29832 10331 I Glide : at com.bumptech.glide.load.data.l.d(Unknown Source:98) 03-17 00:14:56.848 29832 10331 I Glide : ... 11 more 03-17 00:14:56.969 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 47MB AllocSpace bytes, 2(72KB) LOS objects, 75% free, 18MB/74MB, paused 788us,1.151ms total 144.295ms 03-17 00:14:57.115 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 6100KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 13MB/54MB, paused 214us,585us total 44.299ms 03-17 00:14:57.356 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 148KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 13MB/54MB, paused 215us,539us total 40.239ms 03-17 00:14:57.699 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 2592KB AllocSpace bytes, 4(144KB) LOS objects, 75% free, 13MB/54MB, paused 755us,638us total 42.567ms 03-17 00:14:58.150 29832 29832 I ActivityThread: Schedule relaunch activity: com.x8bit.bitwarden.MainActivity --------- switch to events 03-17 00:14:58.151 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=pausing] 03-17 00:14:58.153 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=0ms] 03-17 00:14:58.155 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleRelaunchActivity,time=0ms] 03-17 00:14:58.160 29832 29832 I wm_on_destroy_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performDestroy,time=0ms] --------- switch to main 03-17 00:14:58.171 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 5900KB AllocSpace bytes, 4(208KB) LOS objects, 75% free, 9180KB/35MB, paused 510us,1.407ms total 70.395ms --------- switch to system 03-17 00:14:58.179 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider 03-17 00:14:58.180 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider --------- switch to events 03-17 00:14:58.182 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=17ms] 03-17 00:14:58.190 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms] 03-17 00:14:58.190 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms] 03-17 00:14:58.190 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topWhenResuming] 03-17 00:14:58.210 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0] --------- switch to main 03-17 00:14:58.213 29832 29832 I ActivityThread: Schedule relaunch activity: com.x8bit.bitwarden.MainActivity --------- switch to events 03-17 00:14:58.215 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=pausing] 03-17 00:14:58.215 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=1ms] 03-17 00:14:58.215 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleRelaunchActivity,time=0ms] 03-17 00:14:58.217 29832 29832 I wm_on_destroy_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performDestroy,time=0ms] --------- switch to system 03-17 00:14:58.225 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider 03-17 00:14:58.225 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider --------- switch to events 03-17 00:14:58.227 29832 29832 I wm_on_create_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performCreate,time=8ms] 03-17 00:14:58.233 29832 29832 I wm_on_start_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=handleStartActivity,time=0ms] 03-17 00:14:58.234 29832 29832 I wm_on_resume_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=RESUME_ACTIVITY,time=0ms] 03-17 00:14:58.234 29832 29832 I wm_on_top_resumed_gained_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topWhenResuming] 03-17 00:14:58.249 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=reportDrawFinished seqId=0] --------- switch to main 03-17 00:14:58.379 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 1865KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 9927KB/38MB, paused 473us,1.282ms total 67.377ms 03-17 00:14:58.530 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 1226KB AllocSpace bytes, 1(16KB) LOS objects, 75% free, 8813KB/34MB, paused 337us,953us total 49.293ms 03-17 00:14:58.784 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 112KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 322us,962us total 51.671ms 03-17 00:14:59.147 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 422us,1.115ms total 60.619ms 03-17 00:14:59.599 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 319us,996us total 51.269ms 03-17 00:15:00.145 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8829KB/34MB, paused 320us,864us total 43.334ms 03-17 00:15:00.795 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 128KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 337us,863us total 48.662ms 03-17 00:15:01.543 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 320us,905us total 46.934ms 03-17 00:15:02.396 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 96KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8797KB/34MB, paused 334us,943us total 50.578ms 03-17 00:15:03.342 29832 27875 I com.x8bit.bitwarden: Explicit concurrent mark compact GC freed 120KB AllocSpace bytes, 0(0B) LOS objects, 75% free, 8837KB/34MB, paused 310us,954us total 44.999ms 03-17 00:15:03.394 29832 29832 W WindowOnBackDispatcher: OnBackInvokedCallback is not enabled for the application. 03-17 00:15:03.394 29832 29832 W WindowOnBackDispatcher: Set 'android:enableOnBackInvokedCallback="true"' in the application manifest. --------- switch to events 03-17 00:15:03.436 29832 29832 I viewroot_draw_event: [window=VRI[Pop-Up Window],event=reportDrawFinished seqId=0] --------- switch to main 03-17 00:15:03.451 29832 29832 D InsetsController: show(ime(), fromIme=false) 03-17 00:15:03.452 29832 29832 I ImeTracker: com.x8bit.bitwarden:3878917e: onRequestShow at ORIGIN_CLIENT reason SHOW_SOFT_INPUT_BY_INSETS_API fromUser false --------- switch to system 03-17 00:15:03.453 29832 29832 D InsetsController: Setting requestedVisibleTypes to -1 (was -9) --------- switch to main 03-17 00:15:03.460 29832 29832 I ImeTracker: com.x8bit.bitwarden:89450226: onRequestShow at ORIGIN_CLIENT reason SHOW_SOFT_INPUT fromUser false 03-17 00:15:03.460 29832 29832 D InsetsController: show(ime(), fromIme=false) 03-17 00:15:03.460 29832 29832 I ImeTracker: com.x8bit.bitwarden:89450226: onCancelled at PHASE_CLIENT_REPORT_REQUESTED_VISIBLE_TYPES --------- switch to events 03-17 00:15:03.468 29832 10249 I viewroot_draw_event: [window=VRI[Pop-Up Window],event=reportDrawFinished seqId=0] --------- switch to main 03-17 00:15:03.889 29832 29832 W InteractionJankMonitor: Initializing without READ_DEVICE_CONFIG permission. enabled=false, interval=1, missedFrameThreshold=3, frameTimeThreshold=64, package=com.x8bit.bitwarden --------- switch to events 03-17 00:15:03.890 29832 27934 I jank_cuj_events_begin_request: [CUJ Type=80,Unix Time Ns=1742170503890053s,Elapsed Time Ns=103726589411.055s,Uptime Ns=76543122448.181s,Tag=0@1@com.x8bit.bitwarden] --------- switch to main 03-17 00:15:03.948 29832 29832 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=false callback=android.view.ViewRootImpl$$ExternalSyntheticLambda13@29765f6 --------- switch to events 03-17 00:15:04.188 29832 27934 I jank_cuj_events_end_request: [CUJ Type=80,Unix Time Ns=1742170504188253s,Elapsed Time Ns=103726887611.617s,Uptime Time Ns=76543420648.661s] --------- switch to main 03-17 00:15:04.188 29832 29832 I ImeTracker: com.x8bit.bitwarden:3878917e: onShown --------- switch to events 03-17 00:15:13.784 29832 29832 I wm_on_top_resumed_lost_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=topStateChangedWhenResumed] 03-17 00:15:16.372 29832 29832 I wm_on_paused_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=performPause,time=0ms] --------- switch to main 03-17 00:15:16.759 29832 29832 D VRI[MainActivity]: visibilityChanged oldVisibility=true newVisibility=false --------- switch to events 03-17 00:15:16.773 29832 29832 I viewroot_draw_event: [window=VRI[MainActivity],event=Not drawing due to not visible. Reason=!mAppVisible && !mForceDecorViewVisibility] 03-17 00:15:16.777 29832 29832 I wm_on_stop_called: [Token=126867849,Component Name=com.x8bit.bitwarden.MainActivity,Reason=STOP_ACTIVITY_ITEM,time=2ms] --------- switch to main 03-17 00:15:16.782 29832 29832 D InsetsController: hide(ime(), fromIme=false) 03-17 00:15:16.784 29832 29832 I ImeTracker: com.x8bit.bitwarden:63385b6e: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT_BY_INSETS_API fromUser false 03-17 00:15:16.784 29832 29832 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=false callback=android.view.ImeBackAnimationController@b1c47b4 --------- switch to system 03-17 00:15:16.784 29832 29832 D InsetsController: Setting requestedVisibleTypes to -9 (was -1) --------- switch to events 03-17 00:15:16.786 29832 27934 I jank_cuj_events_begin_request: [CUJ Type=81,Unix Time Ns=1742170516786641s,Elapsed Time Ns=103739485999.603s,Uptime Ns=76556019036.81s,Tag=1@1@com.x8bit.bitwarden] --------- switch to system 03-17 00:15:17.079 29832 29832 E ActivityThread: Failed to find provider info for com.android.chrome.AutofillThirdPartyModeContentProvider 03-17 00:15:17.080 29832 29832 E ActivityThread: Failed to find provider info for com.chrome.beta.AutofillThirdPartyModeContentProvider --------- switch to events 03-17 00:15:17.082 29832 27934 I jank_cuj_events_end_request: [CUJ Type=81,Unix Time Ns=1742170517082097s,Elapsed Time Ns=103739781458.465s,Uptime Time Ns=76556314495.795s] --------- switch to main 03-17 00:15:17.093 29832 29832 W RemoteInputConnectionImpl: requestCursorUpdates on inactive InputConnection ```

GiteaMirror commented

@felmey commented on GitHub (Mar 21, 2025):

Has anyone found a fix for this? I'm starting to explore other password manager options as this bug has made the Android app unusable.

@felmey commented on GitHub (Mar 21, 2025): Has anyone found a fix for this? I'm starting to explore other password manager options as this bug has made the Android app unusable.

GiteaMirror commented

@felmey commented on GitHub (Mar 25, 2025):

Accidentally closed. Work around found but issue is not solved as app is still hard broken.

@felmey commented on GitHub (Mar 25, 2025): Accidentally closed. Work around found but issue is not solved as app is still hard broken.

GiteaMirror commented

@SaintPatrck commented on GitHub (Mar 26, 2025):

@felmey I linked a PR that may be related to your issue. It will be in the next release. You can get a pre-release build with the change from https://github.com/bitwarden/android/actions/runs/13977984201. Let us know if it resolves your issue. If not we will continue to monitor and investigate.

@SaintPatrck commented on GitHub (Mar 26, 2025): @felmey I linked a PR that may be related to your issue. It will be in the next release. You can get a pre-release build with the change from https://github.com/bitwarden/android/actions/runs/13977984201. Let us know if it resolves your issue. If not we will continue to monitor and investigate.

GiteaMirror commented

@felmey commented on GitHub (Mar 29, 2025):

@felmey I linked a PR that may be related to your issue. It will be in the next release. You can get a pre-release build with the change from https://github.com/bitwarden/android/actions/runs/13977984201. Let us know if it resolves your issue. If not we will continue to monitor and investigate.

@SaintPatrck The pre-release build you posted has worked without this error occuring. I'll close this issue. Thank you.

@felmey commented on GitHub (Mar 29, 2025): > [@felmey](https://github.com/felmey) I linked a PR that may be related to your issue. It will be in the next release. You can get a pre-release build with the change from https://github.com/bitwarden/android/actions/runs/13977984201. Let us know if it resolves your issue. If not we will continue to monitor and investigate. @SaintPatrck The pre-release build you posted has worked without this error occuring. I'll close this issue. Thank you.

GiteaMirror commented

@felmey commented on GitHub (Mar 30, 2025):

Well, after a day running The pre-release build this error started again. Completely logs me out and turns off biometrics and resets timeout to default. It specifically did this on a system reboot/restart.

@felmey commented on GitHub (Mar 30, 2025): Well, after a day running The pre-release build this error started again. Completely logs me out and turns off biometrics and resets timeout to default. It specifically did this on a system reboot/restart.

GiteaMirror commented

@felmey commented on GitHub (Mar 31, 2025):

It is now producing this bug randomly multiple times a day.

@felmey commented on GitHub (Mar 31, 2025): It is now producing this bug randomly multiple times a day.

GiteaMirror commented

@mvthde commented on GitHub (Mar 31, 2025):

It is now producing this bug randomly multiple times a day.

Can confirm this behavior with app version 2025.2.0 and before (since 2025.x update).

@mvthde commented on GitHub (Mar 31, 2025): > It is now producing this bug randomly multiple times a day. Can confirm this behavior with app version 2025.2.0 and before (since 2025.x update).

GiteaMirror commented

@simeneriks1 commented on GitHub (Apr 1, 2025):

I have had the same behaviour for the past month.

What happened today was:

I logged into a web page, so I opened Bitwarden via my keyboard popup on SwiftKey, authenticated with my existing biometric (fingerprint), retrieved (autofilled) my password and logged in as normal to the page.
3 minutes later (or less) I proceeded to open my Bitwarden app manually from my app launcher. I briefly (for 1 second) see the main page on the Bitwarden app with all my favourited elements and passwords, and then I get thrown out where I need to put in my Bitwarden master password to log in again. It does not seem to be connected to app restarts or crashes for me.
I entered my master password and logged in. Biometrics, vault timeout, pin setting and such were all back to its default values or removed.
I proceed to re-enable biometrics, pin-code and vault timeout to 30 minutes, with "Lock".

This has been happening very often the past month and a half I would assume. It has gone from being an inconvenience to an absolute annoyance, and I will gladly help test pre-release builds if you need help.

EDIT: I am also on a Pixel device, the Google Pixel 9 Pro.

@simeneriks1 commented on GitHub (Apr 1, 2025): I have had the same behaviour for the past month. What happened today was: 1. I logged into a web page, so I opened Bitwarden via my keyboard popup on SwiftKey, authenticated with my existing biometric (fingerprint), retrieved (autofilled) my password and logged in as normal to the page. 2. 3 minutes later (or less) I proceeded to open my Bitwarden app manually from my app launcher. I briefly (for 1 second) see the main page on the Bitwarden app with all my favourited elements and passwords, and then I get thrown out where I need to put in my Bitwarden master password to log in again. It does not seem to be connected to app restarts or crashes for me. 3. I entered my master password and logged in. Biometrics, vault timeout, pin setting and such were all back to its default values or removed. 4. I proceed to re-enable biometrics, pin-code and vault timeout to 30 minutes, with "Lock". This has been happening very often the past month and a half I would assume. It has gone from being an inconvenience to an absolute annoyance, and I will gladly help test pre-release builds if you need help. EDIT: I am also on a Pixel device, the _Google Pixel 9 Pro._

GiteaMirror commented

@regeneratorre4 commented on GitHub (Apr 12, 2025):

I am severely disappointed in the lack of priority the bitwarden team has displayed in resolving this issue. This issue was reported originally over 2 months ago, a fix turnaround this long is completely unacceptable. As a paying customer, this is not the level of customer service I expect. As such, I will be disabling all my premium subscriptions for bitwarden until this issue is resolved, and migrating to a reliable password manager if this issue is not resolved in a timely manner. I suggest everyone impacted do the same.

@regeneratorre4 commented on GitHub (Apr 12, 2025): I am severely disappointed in the lack of priority the bitwarden team has displayed in resolving this issue. This issue was reported originally over 2 months ago, a fix turnaround this long is completely unacceptable. As a paying customer, this is not the level of customer service I expect. As such, I will be disabling all my premium subscriptions for bitwarden until this issue is resolved, and migrating to a reliable password manager if this issue is not resolved in a timely manner. I suggest everyone impacted do the same.

GiteaMirror commented

@albin-engstrom commented on GitHub (Apr 12, 2025):

This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL.

Unlocking with biometrics seem to enable properly, but never worked. After doing so a few times I started to look into it.

And I've found that if I pressed "Lock Now" or "Log out" on the "Account Security" page the biometrics option was visibly changed to disabled before leaving the page. And when unlocking or logging in again, the setting was indeed disabled.

I've also found that if I enabled "Unlock with Biometrics" and then also changed the "Session Timeout" before leaving the changes stuck and biometrics worked correctly.

I just found this, so I don't know if it'll disable again after some time as it seems to do for some. But it seems to work for now.
I'll update this if it does disable at a later point.

@albin-engstrom commented on GitHub (Apr 12, 2025): This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL. Unlocking with biometrics seem to enable properly, but never worked. After doing so a few times I started to look into it. And I've found that if I pressed "Lock Now" or "Log out" on the "Account Security" page the biometrics option was visibly changed to disabled before leaving the page. And when unlocking or logging in again, the setting was indeed disabled. I've also found that if I enabled "Unlock with Biometrics" and then also changed the "Session Timeout" before leaving the changes stuck and biometrics worked correctly. I just found this, so I don't know if it'll disable again after some time as it seems to do for some. But it seems to work for now. I'll update this if it does disable at a later point.

GiteaMirror commented

@jtruland commented on GitHub (Apr 12, 2025):

On the latest version of server and Android/browser extension I haven't
seen this behavior in at least the past week

On Sat, Apr 12, 2025, 11:25 Albin Engström @.***> wrote:

This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL.

Unlocking with biometrics seem to enable properly, but never worked. After
doing so a few times I started to look into it.

And I've found that if I pressed "Lock Now" or "Log out" on the "Account
Security" page the biometrics option was visibly changed to disabled before
leaving the page. And when unlocking or logging in again, the setting was
indeed disabled.

I've also found that if I enabled "Unlock with Biometrics" and then also
changed the "Session Timeout" before leaving the changes stuck and
biometrics worked correctly.

I just found this, so I don't know if it'll disable again after some time
as it seems to do for some. But it seems to work for now.
I'll update this if it does disable at a later point.

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE
.
You are receiving this because you commented.Message ID:
@.***>
albin-engstrom left a comment (bitwarden/android#4650)
https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429

This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL.

Unlocking with biometrics seem to enable properly, but never worked. After
doing so a few times I started to look into it.

And I've found that if I pressed "Lock Now" or "Log out" on the "Account
Security" page the biometrics option was visibly changed to disabled before
leaving the page. And when unlocking or logging in again, the setting was
indeed disabled.

I've also found that if I enabled "Unlock with Biometrics" and then also
changed the "Session Timeout" before leaving the changes stuck and
biometrics worked correctly.

I just found this, so I don't know if it'll disable again after some time
as it seems to do for some. But it seems to work for now.
I'll update this if it does disable at a later point.

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE
.
You are receiving this because you commented.Message ID:
@.***>

@jtruland commented on GitHub (Apr 12, 2025): On the latest version of server and Android/browser extension I haven't seen this behavior in at least the past week On Sat, Apr 12, 2025, 11:25 Albin Engström ***@***.***> wrote: > This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL. > > Unlocking with biometrics seem to enable properly, but never worked. After > doing so a few times I started to look into it. > > And I've found that if I pressed "Lock Now" or "Log out" on the "Account > Security" page the biometrics option was visibly changed to disabled before > leaving the page. And when unlocking or logging in again, the setting was > indeed disabled. > > I've also found that if I enabled "Unlock with Biometrics" and then also > changed the "Session Timeout" before leaving the changes stuck and > biometrics worked correctly. > > I just found this, so I don't know if it'll disable again after some time > as it seems to do for some. But it seems to work for now. > I'll update this if it does disable at a later point. > > — > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE> > . > You are receiving this because you commented.Message ID: > ***@***.***> > *albin-engstrom* left a comment (bitwarden/android#4650) > <https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429> > > This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL. > > Unlocking with biometrics seem to enable properly, but never worked. After > doing so a few times I started to look into it. > > And I've found that if I pressed "Lock Now" or "Log out" on the "Account > Security" page the biometrics option was visibly changed to disabled before > leaving the page. And when unlocking or logging in again, the setting was > indeed disabled. > > I've also found that if I enabled "Unlock with Biometrics" and then also > changed the "Session Timeout" before leaving the changes stuck and > biometrics worked correctly. > > I just found this, so I don't know if it'll disable again after some time > as it seems to do for some. But it seems to work for now. > I'll update this if it does disable at a later point. > > — > Reply to this email directly, view it on GitHub > <https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

GiteaMirror commented

@jtruland commented on GitHub (Apr 12, 2025):

I also moved my installation from /root to using a specific bitwarden user,
during that time. I'm not sure if either or both are contributing.

On Sat, Apr 12, 2025, 12:34 Jon Truland @.***> wrote:

On the latest version of server and Android/browser extension I haven't
seen this behavior in at least the past week

On Sat, Apr 12, 2025, 11:25 Albin Engström @.***>
wrote:

This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL.

Unlocking with biometrics seem to enable properly, but never worked.
After doing so a few times I started to look into it.

And I've found that if I pressed "Lock Now" or "Log out" on the "Account
Security" page the biometrics option was visibly changed to disabled before
leaving the page. And when unlocking or logging in again, the setting was
indeed disabled.

I've also found that if I enabled "Unlock with Biometrics" and then also
changed the "Session Timeout" before leaving the changes stuck and
biometrics worked correctly.

I just found this, so I don't know if it'll disable again after some time
as it seems to do for some. But it seems to work for now.
I'll update this if it does disable at a later point.

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE
.
You are receiving this because you commented.Message ID:
@.***>
albin-engstrom left a comment (bitwarden/android#4650)
https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429

This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL.

Unlocking with biometrics seem to enable properly, but never worked.
After doing so a few times I started to look into it.

And I've found that if I pressed "Lock Now" or "Log out" on the "Account
Security" page the biometrics option was visibly changed to disabled before
leaving the page. And when unlocking or logging in again, the setting was
indeed disabled.

I've also found that if I enabled "Unlock with Biometrics" and then also
changed the "Session Timeout" before leaving the changes stuck and
biometrics worked correctly.

I just found this, so I don't know if it'll disable again after some time
as it seems to do for some. But it seems to work for now.
I'll update this if it does disable at a later point.

—
Reply to this email directly, view it on GitHub
https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE
.
You are receiving this because you commented.Message ID:
@.***>

@jtruland commented on GitHub (Apr 12, 2025): I also moved my installation from /root to using a specific bitwarden user, during that time. I'm not sure if either or both are contributing. On Sat, Apr 12, 2025, 12:34 Jon Truland ***@***.***> wrote: > On the latest version of server and Android/browser extension I haven't > seen this behavior in at least the past week > > On Sat, Apr 12, 2025, 11:25 Albin Engström ***@***.***> > wrote: > >> This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL. >> >> Unlocking with biometrics seem to enable properly, but never worked. >> After doing so a few times I started to look into it. >> >> And I've found that if I pressed "Lock Now" or "Log out" on the "Account >> Security" page the biometrics option was visibly changed to disabled before >> leaving the page. And when unlocking or logging in again, the setting was >> indeed disabled. >> >> I've also found that if I enabled "Unlock with Biometrics" and then also >> changed the "Session Timeout" before leaving the changes stuck and >> biometrics worked correctly. >> >> I just found this, so I don't know if it'll disable again after some time >> as it seems to do for some. But it seems to work for now. >> I'll update this if it does disable at a later point. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE> >> . >> You are receiving this because you commented.Message ID: >> ***@***.***> >> *albin-engstrom* left a comment (bitwarden/android#4650) >> <https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429> >> >> This bug is happening for me too on version 2025.3.0 on a Pixel 9 Pro XL. >> >> Unlocking with biometrics seem to enable properly, but never worked. >> After doing so a few times I started to look into it. >> >> And I've found that if I pressed "Lock Now" or "Log out" on the "Account >> Security" page the biometrics option was visibly changed to disabled before >> leaving the page. And when unlocking or logging in again, the setting was >> indeed disabled. >> >> I've also found that if I enabled "Unlock with Biometrics" and then also >> changed the "Session Timeout" before leaving the changes stuck and >> biometrics worked correctly. >> >> I just found this, so I don't know if it'll disable again after some time >> as it seems to do for some. But it seems to work for now. >> I'll update this if it does disable at a later point. >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/bitwarden/android/issues/4650#issuecomment-2798874429>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AJAX6KEEHRFV23UT3XKMSVT2ZEWAJAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3TINBSHE> >> . >> You are receiving this because you commented.Message ID: >> ***@***.***> >> >

GiteaMirror commented

@simeneriks1 commented on GitHub (Apr 29, 2025):

I am still facing this issue, is there anything I can do in order to help debug this issue in more detail? @SaintPatrck

@simeneriks1 commented on GitHub (Apr 29, 2025): I am still facing this issue, is there anything I can do in order to help debug this issue in more detail? @SaintPatrck

GiteaMirror commented

@felmey commented on GitHub (Apr 29, 2025):

I'm also still experiencing this bug. I even posted a review on the play store detailing the issue. Due to the lack of response, I am starting to consider this abandonware at this point. I've been slowly migrating to another password management solution.

@felmey commented on GitHub (Apr 29, 2025): I'm also still experiencing this bug. I even posted a review on the play store detailing the issue. Due to the lack of response, I am starting to consider this abandonware at this point. I've been slowly migrating to another password management solution.

GiteaMirror commented

@alexzeitgeist commented on GitHub (May 5, 2025):

I am surprised there isn't more feedback about the status quo from the team. This bug is quite severe, and it has affected me more than once (I don't have access to my master password when I travel...). I was forced to downgrade to the old codebase (2024.10.0), which doesn't exhibit this issue.

@alexzeitgeist commented on GitHub (May 5, 2025): I am surprised there isn't more feedback about the status quo from the team. This bug is quite severe, and it has affected me more than once (I don't have access to my master password when I travel...). I was forced to downgrade to the old codebase (2024.10.0), which doesn't exhibit this issue.

GiteaMirror commented

@felmey commented on GitHub (May 5, 2025):

@alexzeitgeist

Is that the latest version that still works? If so I will try to do that same.

-------- Original Message --------
On 5/5/25 21:49, Alexander wrote:

alexzeitgeist left a comment (bitwarden/android#4650)

I am surprised there isn't more feedback about the status quo from the team. This bug is quite severe, and it has affected me more than once (I don't have access to my master password when I travel...). I was forced to downgrade to the old codebase (2024.10.0), which doesn't exhibit this issue.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

@felmey commented on GitHub (May 5, 2025): @alexzeitgeist Is that the latest version that still works? If so I will try to do that same. -------- Original Message -------- On 5/5/25 21:49, Alexander wrote: > alexzeitgeist left a comment [(bitwarden/android#4650)](https://github.com/bitwarden/android/issues/4650#issuecomment-2852163127) > > I am surprised there isn't more feedback about the status quo from the team. This bug is quite severe, and it has affected me more than once (I don't have access to my master password when I travel...). I was forced to downgrade to the old codebase (2024.10.0), which doesn't exhibit this issue. > > — > Reply to this email directly, [view it on GitHub](https://github.com/bitwarden/android/issues/4650#issuecomment-2852163127), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AD5UHVHNMWTPJFNAHQKEGRL2466DRAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJSGE3DGMJSG4). > You are receiving this because you modified the open/close state.Message ID: ***@***.***>

GiteaMirror commented

@alexzeitgeist commented on GitHub (May 5, 2025):

@felmey yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile

I just have to be careful not to accidently click the "update" button in Google Play.

@alexzeitgeist commented on GitHub (May 5, 2025): @felmey yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile I just have to be careful not to accidently click the "update" button in Google Play.

GiteaMirror commented

@alexzeitgeist commented on GitHub (May 15, 2025):

Edit: it lasted one day. Now it is asking for the master password again. 🤨

Original message: just upgraded to Samsung One UI 7 (Android 15) and decided to give the updated Bitwarden mobile app another try. So far, so good - the app kept my biometric credentials and hasn't asked for my master password again.

@alexzeitgeist commented on GitHub (May 15, 2025): Edit: it lasted one day. Now it is asking for the master password again. 🤨 Original message: just upgraded to Samsung One UI 7 (Android 15) and decided to give the updated Bitwarden mobile app another try. So far, so good - the app kept my biometric credentials and hasn't asked for my master password again.

GiteaMirror commented

https://github.com/bitwarden/mobile

@felmey commented on GitHub (May 15, 2025):

@alexzeitgeist I installed the C# version you posted and it has worked perfectly ever since. Clearly the fork using the new codebase has serious errors/bugs that aren't being addressed.

I assume eventually I will still need to find a new password management solution since Bitwarden no longer appears to be developing the C# version. But for now your suggestion has made this product usable once more.

Thanks

-------- Original Message --------
On 5/5/25 12:57, Alexander wrote:

alexzeitgeist left a comment (bitwarden/android#4650)

@.***(https://github.com/felmey) yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile

I just have to be careful not to accidently click the "update" button in Google Play.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@felmey commented on GitHub (May 15, 2025): @alexzeitgeist I installed the C# version you posted and it has worked perfectly ever since. Clearly the fork using the new codebase has serious errors/bugs that aren't being addressed. https://github.com/bitwarden/mobile I assume eventually I will still need to find a new password management solution since Bitwarden no longer appears to be developing the C# version. But for now your suggestion has made this product usable once more. Thanks -------- Original Message -------- On 5/5/25 12:57, Alexander wrote: > alexzeitgeist left a comment [(bitwarden/android#4650)](https://github.com/bitwarden/android/issues/4650#issuecomment-2852188767) > > ***@***.***(https://github.com/felmey) yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile > > I just have to be careful not to accidently click the "update" button in Google Play. > > — > Reply to this email directly, [view it on GitHub](https://github.com/bitwarden/android/issues/4650#issuecomment-2852188767), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AD5UHVCTQ3AOOAIYKT7IWGT2467ENAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJSGE4DQNZWG4). > You are receiving this because you were mentioned.Message ID: ***@***.***>

GiteaMirror commented

@felmey commented on GitHub (May 28, 2025):

Just a quick update, I've been using the C# codebase version recommended by @alexzeitgeist and it has worked PERFECTLY for 2 weeks. No issues whatsoever. As he said, the only thing you have to be careful of is letting Google Play Store update you to the hopelessly flawed/broken current version of the app.

Hopefully Bitwarden doesn't break the server software at some point like they've done with the Android App and we can continue to use the legacy version.

I'll keep this issue open since the current codebase is still broken.

@felmey yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile

I just have to be careful not to accidently click the "update" button in Google Play.

@felmey commented on GitHub (May 28, 2025): Just a quick update, I've been using the C# codebase version recommended by @alexzeitgeist and it has worked PERFECTLY for 2 weeks. No issues whatsoever. As he said, the only thing you have to be careful of is letting Google Play Store update you to the hopelessly flawed/broken current version of the app. Hopefully Bitwarden doesn't break the server software at some point like they've done with the Android App and we can continue to use the legacy version. I'll keep this issue open since the current codebase is still broken. > [@felmey](https://github.com/felmey) yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile > > I just have to be careful not to accidently click the "update" button in Google Play.

GiteaMirror commented

@jtruland commented on GitHub (May 28, 2025):

Just a quick update, I've been using the C# codebase version recommended by @alexzeitgeist and it has worked PERFECTLY for 2 weeks. No issues whatsoever. As he said, the only thing you have to be careful of is letting Google Play Store update you to the hopelessly flawed/broken current version of the app.

Hopefully Bitwarden doesn't break the server software at some point like they've done with the Android App and we can continue to use the legacy version.

I'll keep this issue open since the current codebase is still broken.

@felmey yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile
I just have to be careful not to accidently click the "update" button in Google Play.

I haven't experienced the issue, using the new codebase/clients, since my last posts in April. I'm not exactly sure whether my reconfiguration of docker compose to use BW specific GUIDs and file permissions to use a non-root user had any impact.

@jtruland commented on GitHub (May 28, 2025): > Just a quick update, I've been using the C# codebase version recommended by [@alexzeitgeist](https://github.com/alexzeitgeist) and it has worked PERFECTLY for 2 weeks. No issues whatsoever. As he said, the only thing you have to be careful of is letting Google Play Store update you to the hopelessly flawed/broken current version of the app. > > Hopefully Bitwarden doesn't break the server software at some point like they've done with the Android App and we can continue to use the legacy version. > > I'll keep this issue open since the current codebase is still broken. > > > [@felmey](https://github.com/felmey) yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile > > I just have to be careful not to accidently click the "update" button in Google Play. I haven't experienced the issue, using the new codebase/clients, since my last posts in April. I'm not exactly sure whether my reconfiguration of docker compose to use BW specific GUIDs and file permissions to use a non-root user had any impact.

GiteaMirror commented

@felmey commented on GitHub (May 28, 2025):

Interesting... I'm using Bitwarden server via docker but I've always ran it under a non-root user... And I still have the issue.

Sent from ProtonMail, encrypted email based in Switzerland.

Sent from Proton Mail Android

-------- Original Message --------
On 5/28/25 14:12, jtruland wrote:

jtruland left a comment (bitwarden/android#4650)

Just a quick update, I've been using the C# codebase version recommended by @.***(https://github.com/alexzeitgeist) and it has worked PERFECTLY for 2 weeks. No issues whatsoever. As he said, the only thing you have to be careful of is letting Google Play Store update you to the hopelessly flawed/broken current version of the app.

Hopefully Bitwarden doesn't break the server software at some point like they've done with the Android App and we can continue to use the legacy version.

I'll keep this issue open since the current codebase is still broken.

@.***(https://github.com/felmey) yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile
I just have to be careful not to accidently click the "update" button in Google Play.

I haven't experienced the issue, using the new codebase/clients, since my last posts in April. I'm not exactly sure whether my reconfiguration of docker compose to use BW specific GUIDs and file permissions to use a non-root user had any impact.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@felmey commented on GitHub (May 28, 2025): Interesting... I'm using Bitwarden server via docker but I've always ran it under a non-root user... And I still have the issue. Sent from ProtonMail, encrypted email based in Switzerland. Sent from Proton Mail Android -------- Original Message -------- On 5/28/25 14:12, jtruland wrote: > jtruland left a comment [(bitwarden/android#4650)](https://github.com/bitwarden/android/issues/4650#issuecomment-2917199648) > >> Just a quick update, I've been using the C# codebase version recommended by ***@***.***(https://github.com/alexzeitgeist) and it has worked PERFECTLY for 2 weeks. No issues whatsoever. As he said, the only thing you have to be careful of is letting Google Play Store update you to the hopelessly flawed/broken current version of the app. >> >> Hopefully Bitwarden doesn't break the server software at some point like they've done with the Android App and we can continue to use the legacy version. >> >> I'll keep this issue open since the current codebase is still broken. >> >>> ***@***.***(https://github.com/felmey) yup, it was the last version of the C# codebase. See here: https://github.com/bitwarden/mobile >>> I just have to be careful not to accidently click the "update" button in Google Play. > > I haven't experienced the issue, using the new codebase/clients, since my last posts in April. I'm not exactly sure whether my reconfiguration of docker compose to use BW specific GUIDs and file permissions to use a non-root user had any impact. > > — > Reply to this email directly, [view it on GitHub](https://github.com/bitwarden/android/issues/4650#issuecomment-2917199648), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AD5UHVAG7JBYKTEOAIC2O733AX4ALAVCNFSM6AAAAABWFH7J3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJXGE4TSNRUHA). > You are receiving this because you were mentioned.Message ID: ***@***.***>

GiteaMirror commented

@edent commented on GitHub (Jul 6, 2025):

Happened to me again today. All of a sudden I had to enter my password and go through 2FA. Once in, I had to re-enable biometrics.

Using the latest version from F-Droid. It updated a few days ago and was fine, then suddenly logged out.

Version: 2025.6.1 (20398)
📱 google Pixel 8 Pro 🤖 15@35 📦 prod -fdroid
🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0
💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1

@edent commented on GitHub (Jul 6, 2025): Happened to me *again* today. All of a sudden I had to enter my password and go through 2FA. Once in, I had to re-enable biometrics. Using the latest version from F-Droid. It updated a few days ago and was fine, then suddenly logged out. Version: 2025.6.1 (20398) 📱 google Pixel 8 Pro 🤖 15@35 📦 prod -fdroid 🧱 commit: bitwarden/android/release/hotfix-v2025.6.0-bwpm@e8878d321546a846909c70c00cdf8d7071f0ecf0 💻 build source: bitwarden/android/actions/runs/15984517798/attempts/1

GiteaMirror commented

2025-11-26 23:10:17 -06:00

@leow149 commented on GitHub (Jul 6, 2025):

For me it happens almost every day. I don't get why this issue isn't recognized? Why doesn't it get more attention?

Nothing Phone 2a Plus | Android 15
Bitwarden Version 2025.6.1

@leow149 commented on GitHub (Jul 6, 2025): For me it happens almost every day. I don't get why this issue isn't recognized? Why doesn't it get more attention? Nothing Phone 2a Plus | Android 15 Bitwarden Version 2025.6.1

GiteaMirror commented

@mvthde commented on GitHub (Jul 6, 2025):

I also had this problem and looked in the logs on the server (bwdata/logs/identity/Identity). Found these lines when the logout happened:

2025-07-05 17:22:08.503 +00:00 [Information] Validating premium license for user 05661e4c-0c68-4077-ab50-3b7e5a8f367a("mail@example.com").
2025-07-05 17:22:08.531 +00:00 [Fatal] Unhandled exception: "‘D’ is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 16 | BytePositionInLine: 1."

In the user's license file (bwdata/core/licenses/user/05661e4c-0c68-4077-ab50-3b7e5a8f367a.json) were characters at the end of the JSON that didn't belong there:

  ...
  "Token": "..."
}Ddz_eFb8"
}

I removed the characters and the last } and the problem did not occur again.

When uploading a (new) license file via web vault, the POST request contains the correct JSON. But sometimes it seems to be stored incorrectly on the server (yesterday incorrectly, today correctly).

@mvthde commented on GitHub (Jul 6, 2025): I also had this problem and looked in the logs on the server (`bwdata/logs/identity/Identity`). Found these lines when the logout happened: ``` 2025-07-05 17:22:08.503 +00:00 [Information] Validating premium license for user 05661e4c-0c68-4077-ab50-3b7e5a8f367a("mail@example.com"). 2025-07-05 17:22:08.531 +00:00 [Fatal] Unhandled exception: "‘D’ is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 16 | BytePositionInLine: 1." ``` In the user's license file (`bwdata/core/licenses/user/05661e4c-0c68-4077-ab50-3b7e5a8f367a.json`) were characters at the end of the JSON that didn't belong there: ``` ... "Token": "..." }Ddz_eFb8" } ``` I removed the characters and the last } and the problem did not occur again. When uploading a (new) license file via web vault, the POST request contains the correct JSON. But sometimes it seems to be stored incorrectly on the server (yesterday incorrectly, today correctly).

GiteaMirror commented

2025-11-26 23:10:17 -06:00

@leow149 commented on GitHub (Jul 6, 2025):

Just looked at mine and it looks like this

{
  "LicenseKey": "CENSORED",
  "Id": "CENSORED",
  "Name": "Leo",
  "Email": "CENSORED",
  "Premium": true,
  "MaxStorageGb": 1,
  "Version": 1,
  "Issued": "2025-01-10T15:49:31.6581573Z",
  "Refresh": "2026-01-03T13:42:07Z",
  "Expires": "2026-01-10T13:42:07Z",
  "Trial": false,
  "LicenseType": 0,
  "Hash": "CENSORED",
  "Signature": "CENSORED"
}R97JIeCgCsA="

Could be a problem, right?

@leow149 commented on GitHub (Jul 6, 2025): Just looked at mine and it looks like this ``` { "LicenseKey": "CENSORED", "Id": "CENSORED", "Name": "Leo", "Email": "CENSORED", "Premium": true, "MaxStorageGb": 1, "Version": 1, "Issued": "2025-01-10T15:49:31.6581573Z", "Refresh": "2026-01-03T13:42:07Z", "Expires": "2026-01-10T13:42:07Z", "Trial": false, "LicenseType": 0, "Hash": "CENSORED", "Signature": "CENSORED" }R97JIeCgCsA=" ``` Could be a problem, right?

GiteaMirror commented

2025-11-26 23:10:17 -06:00

@mvthde commented on GitHub (Jul 6, 2025):

Just looked at mine and it looks like this

{
  "LicenseKey": "CENSORED",
  "Id": "CENSORED",
  "Name": "Leo",
  "Email": "CENSORED",
  "Premium": true,
  "MaxStorageGb": 1,
  "Version": 1,
  "Issued": "2025-01-10T15:49:31.6581573Z",
  "Refresh": "2026-01-03T13:42:07Z",
  "Expires": "2026-01-10T13:42:07Z",
  "Trial": false,
  "LicenseType": 0,
  "Hash": "CENSORED",
  "Signature": "CENSORED"
}R97JIeCgCsA="

Could be a problem, right?

Yes, remove R97JIeCgCsA=" and it should work.

@mvthde commented on GitHub (Jul 6, 2025): > Just looked at mine and it looks like this > > ``` > { > "LicenseKey": "CENSORED", > "Id": "CENSORED", > "Name": "Leo", > "Email": "CENSORED", > "Premium": true, > "MaxStorageGb": 1, > "Version": 1, > "Issued": "2025-01-10T15:49:31.6581573Z", > "Refresh": "2026-01-03T13:42:07Z", > "Expires": "2026-01-10T13:42:07Z", > "Trial": false, > "LicenseType": 0, > "Hash": "CENSORED", > "Signature": "CENSORED" > }R97JIeCgCsA=" > ``` > > Could be a problem, right? Yes, remove `R97JIeCgCsA="` and it should work.

GiteaMirror commented

@leow149 commented on GitHub (Jul 11, 2025):

So, it's been 5 days so far without any problems. Seems like that was the problem.

@leow149 commented on GitHub (Jul 11, 2025): So, it's been 5 days so far without any problems. Seems like that was the problem.

GiteaMirror commented

@felmey commented on GitHub (Jul 11, 2025):

So, it's been 5 days so far without any problems. Seems like that was the problem.

Sounds promising! I also had the extra line of characters at the end of the mentioned JSON file after the Signature line. Although I had quite a few more characters than you two had. I backed up the file and then removed the characters and restarted Bitwarden server. Then I updated the Android Bitwarden app as I was running the old C# version as a workaround. I'll report back.

@felmey commented on GitHub (Jul 11, 2025): > So, it's been 5 days so far without any problems. Seems like that was the problem. Sounds promising! I also had the extra line of characters at the end of the mentioned JSON file after the Signature line. Although I had quite a few more characters than you two had. I backed up the file and then removed the characters and restarted Bitwarden server. Then I updated the Android Bitwarden app as I was running the old C# version as a workaround. I'll report back.

GiteaMirror commented

@felmey commented on GitHub (Jul 11, 2025):

Any idea on how the license JSON file is getting corrupted?

Here is the error that was in ./bwdata/logs/identity/Identity/20250710.txt
(User identity information was redacted.)

2025-07-10 21:07:43.944 +00:00 [Information] Validating premium license for user xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx("user@redacted.com").
2025-07-10 21:07:44.308 +00:00 [Fatal] Unhandled exception: "'8' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 15 | BytePositionInLine: 1."
System.Text.Json.JsonException: '8' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 15 | BytePositionInLine: 1.
 ---> System.Text.Json.JsonReaderException: '8' is invalid after a single JSON value. Expected end of data. LineNumber: 15 | BytePositionInLine: 1.
   at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
   at System.Text.Json.Utf8JsonReader.ConsumeNextToken(Byte marker)
   at System.Text.Json.Utf8JsonReader.ReadSingleSegment()
   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state)
   --- End of inner exception stack trace ---
   at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& state, JsonReaderException ex)
   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state)
   at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 json, JsonTypeInfo`1 jsonTypeInfo)
   at System.Text.Json.JsonSerializer.Deserialize[TValue](String json, JsonSerializerOptions options)
   at Bit.Core.Services.LicensingService.ReadUserLicense(User user) in /home/runner/work/server/server/src/Core/Services/Implementations/LicensingService.cs:line 283
   at Bit.Core.Services.LicensingService.ProcessUserValidationAsync(User user) in /home/runner/work/server/server/src/Core/Services/Implementations/LicensingService.cs:line 209
   at Bit.Core.Services.LicensingService.ValidateUserPremiumAsync(User user) in /home/runner/work/server/server/src/Core/Services/Implementations/LicensingService.cs:line 204
   at Bit.Identity.IdentityServer.ProfileService.GetProfileDataAsync(ProfileDataRequestContext context) in /home/runner/work/server/server/src/Identity/IdentityServer/ProfileService.cs:line 46
   at Duende.IdentityServer.Services.DefaultClaimsService.GetAccessTokenClaimsAsync(ClaimsPrincipal subject, ResourceValidationResult resourceResult, ValidatedRequest request) in /_/src/IdentityServ>
   at Duende.IdentityServer.Services.DefaultTokenService.CreateAccessTokenAsync(TokenCreationRequest request) in /_/src/IdentityServer/Services/Default/DefaultTokenService.cs:line 180
   at Duende.IdentityServer.ResponseHandling.TokenResponseGenerator.ProcessRefreshTokenRequestAsync(TokenRequestValidationResult request) in /_/src/IdentityServer/ResponseHandling/Default/TokenRespo>
   at Duende.IdentityServer.ResponseHandling.TokenResponseGenerator.ProcessAsync(TokenRequestValidationResult request) in /_/src/IdentityServer/ResponseHandling/Default/TokenResponseGenerator.cs:lin>
   at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessTokenRequestAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 133
   at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 81
   at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssue>

@felmey commented on GitHub (Jul 11, 2025): Any idea on how the license JSON file is getting corrupted? Here is the error that was in ./bwdata/logs/identity/Identity/20250710.txt (User identity information was redacted.) ``` 2025-07-10 21:07:43.944 +00:00 [Information] Validating premium license for user xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx("user@redacted.com"). 2025-07-10 21:07:44.308 +00:00 [Fatal] Unhandled exception: "'8' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 15 | BytePositionInLine: 1." System.Text.Json.JsonException: '8' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 15 | BytePositionInLine: 1. ---> System.Text.Json.JsonReaderException: '8' is invalid after a single JSON value. Expected end of data. LineNumber: 15 | BytePositionInLine: 1. at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes) at System.Text.Json.Utf8JsonReader.ConsumeNextToken(Byte marker) at System.Text.Json.Utf8JsonReader.ReadSingleSegment() at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state) --- End of inner exception stack trace --- at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& state, JsonReaderException ex) at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state) at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 json, JsonTypeInfo`1 jsonTypeInfo) at System.Text.Json.JsonSerializer.Deserialize[TValue](String json, JsonSerializerOptions options) at Bit.Core.Services.LicensingService.ReadUserLicense(User user) in /home/runner/work/server/server/src/Core/Services/Implementations/LicensingService.cs:line 283 at Bit.Core.Services.LicensingService.ProcessUserValidationAsync(User user) in /home/runner/work/server/server/src/Core/Services/Implementations/LicensingService.cs:line 209 at Bit.Core.Services.LicensingService.ValidateUserPremiumAsync(User user) in /home/runner/work/server/server/src/Core/Services/Implementations/LicensingService.cs:line 204 at Bit.Identity.IdentityServer.ProfileService.GetProfileDataAsync(ProfileDataRequestContext context) in /home/runner/work/server/server/src/Identity/IdentityServer/ProfileService.cs:line 46 at Duende.IdentityServer.Services.DefaultClaimsService.GetAccessTokenClaimsAsync(ClaimsPrincipal subject, ResourceValidationResult resourceResult, ValidatedRequest request) in /_/src/IdentityServ> at Duende.IdentityServer.Services.DefaultTokenService.CreateAccessTokenAsync(TokenCreationRequest request) in /_/src/IdentityServer/Services/Default/DefaultTokenService.cs:line 180 at Duende.IdentityServer.ResponseHandling.TokenResponseGenerator.ProcessRefreshTokenRequestAsync(TokenRequestValidationResult request) in /_/src/IdentityServer/ResponseHandling/Default/TokenRespo> at Duende.IdentityServer.ResponseHandling.TokenResponseGenerator.ProcessAsync(TokenRequestValidationResult request) in /_/src/IdentityServer/ResponseHandling/Default/TokenResponseGenerator.cs:lin> at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessTokenRequestAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 133 at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 81 at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssue> ```

GiteaMirror commented

@djpeck1 commented on GitHub (Jul 15, 2025):

Bitwarden Unified server version: 2025.7.0
Bitwarden Android app version: 2025.6.1

I thought this issue had been resolved after my self hosted Bitwarden Unified server was updated to version 2025.7.0. I had no unexpected log outs and biometrics resets for over a week. Unfortunately the problem has now returned and every morning when I use Bitwarden on the phone I find that I have been logged out and biometrics reset.

I don't know if the Bitwarden developers are monitoring this thread, but if they are I have included errors in the identity.log that seem to be present when I am getting unexpectedly logged out of the Bitwarden Android app. I don't know if the errors are relevant to the problem, but the errors didn't appear during the week when the Bitwarden Android app was not logging out unexpectedly.

Errors in identity.log ...

2025-07-12` 22:15:59.683 +01:00 [FTL] Unhandled exception: Unexpected end of request content.
Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content.
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Microsoft.AspNetCore.WebUtilities.FormPipeReader.ReadFormAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Http.Features.FormFeature.InnerReadFormAsync(CancellationToken cancellationToken)
   at Duende.IdentityServer.Validation.PostBodySecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/PostBodySecretParser.cs:line 60
   at Duende.IdentityServer.Validation.SecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/SecretParser.cs:line 45
   at Duende.IdentityServer.Validation.ClientSecretValidator.ValidateAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/ClientSecretValidator.cs:line 60
   at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessTokenRequestAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 95
   at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 81
   at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in /_/src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 106

2025-07-12 22:16:01.869 +01:00 [ERR] Connection id "0HNDSHB92AIJU", Request id "0HNDSHB92AIJU:00000001": An unhandled exception was thrown by the application.
Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content.
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Microsoft.AspNetCore.WebUtilities.FormPipeReader.ReadFormAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Http.Features.FormFeature.InnerReadFormAsync(CancellationToken cancellationToken)
   at Duende.IdentityServer.Validation.PostBodySecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/PostBodySecretParser.cs:line 60
   at Duende.IdentityServer.Validation.SecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/SecretParser.cs:line 45
   at Duende.IdentityServer.Validation.ClientSecretValidator.ValidateAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/ClientSecretValidator.cs:line 60
   at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessTokenRequestAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 95
   at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 81
   at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in /_/src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 106
   at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in /_/src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 128
   at Duende.IdentityServer.Hosting.MutualTlsEndpointMiddleware.Invoke(HttpContext context, IAuthenticationSchemeProvider schemes) in /_/src/IdentityServer/Hosting/MutualTlsEndpointMiddleware.cs:line 95
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Duende.IdentityServer.Hosting.DynamicProviders.DynamicSchemeAuthenticationMiddleware.Invoke(HttpContext context) in /_/src/IdentityServer/Hosting/DynamicProviders/DynamicSchemes/DynamicSchemeAuthenticationMiddleware.cs:line 51
   at Duende.IdentityServer.Hosting.BaseUrlMiddleware.Invoke(HttpContext context) in /_/src/IdentityServer/Hosting/BaseUrlMiddleware.cs:line 27
   at Bit.Core.Utilities.CurrentContextMiddleware.Invoke(HttpContext httpContext, ICurrentContext currentContext, GlobalSettings globalSettings) in /source/src/Core/Utilities/CurrentContextMiddleware.cs:line 19
   at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.UsePathBaseMiddleware.InvokeCore(HttpContext context, PathString matchedPath, PathString remainingPath)
   at Bit.Identity.Startup.<>c__DisplayClass10_1.<<Configure>b__2>d.MoveNext() in /source/src/Identity/Startup.cs:line 189
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

2025-07-13 08:44:00.419 +01:00 [ERR] Unexpected end of request content.
Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content.
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.ReadAsyncInternal(Memory`1 destination, CancellationToken cancellationToken)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at System.Text.Json.Serialization.ReadBufferState.ReadFromStreamAsync(Stream utf8Json, CancellationToken cancellationToken, Boolean fillBuffer)
   at System.Text.Json.Serialization.Metadata.JsonTypeInfo`1.DeserializeAsync(Stream utf8Json, CancellationToken cancellationToken)
   at System.Text.Json.Serialization.Metadata.JsonTypeInfo`1.DeserializeAsObjectAsync(Stream utf8Json, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Mvc.Formatters.SystemTextJsonInputFormatter.ReadRequestBodyAsync(InputFormatterContext context, Encoding encoding)
   at Microsoft.AspNetCore.Mvc.Formatters.SystemTextJsonInputFormatter.ReadRequestBodyAsync(InputFormatterContext context, Encoding encoding)
   at Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BodyModelBinder.BindModelAsync(ModelBindingContext bindingContext)
   at Microsoft.AspNetCore.Mvc.ModelBinding.ParameterBinder.BindModelAsync(ActionContext actionContext, IModelBinder modelBinder, IValueProvider valueProvider, ParameterDescriptor parameter, ModelMetadata metadata, Object value, Object container)
   at Microsoft.AspNetCore.Mvc.Controllers.ControllerBinderDelegateProvider.<>c__DisplayClass0_0.<<CreateBinderDelegate>g__Bind|0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean `isCompleted`

I would be interested to know if anyone following this thread and has the unexpected logout and biometrics reset problem and is NOT using an instance of the Bitwarden self hosted server. It might narrow the problem down to a server side issue or Android app issue.

@djpeck1 commented on GitHub (Jul 15, 2025): Bitwarden Unified server version: 2025.7.0 Bitwarden Android app version: 2025.6.1 I thought this issue had been resolved after my self hosted Bitwarden Unified server was updated to version 2025.7.0. I had no unexpected log outs and biometrics resets for over a week. Unfortunately the problem has now returned and every morning when I use Bitwarden on the phone I find that I have been logged out and biometrics reset. I don't know if the Bitwarden developers are monitoring this thread, but if they are I have included errors in the identity.log that seem to be present when I am getting unexpectedly logged out of the Bitwarden Android app. I don't know if the errors are relevant to the problem, but the errors didn't appear during the week when the Bitwarden Android app was not logging out unexpectedly. Errors in identity.log ... ``` 2025-07-12` 22:15:59.683 +01:00 [FTL] Unhandled exception: Unexpected end of request content. Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content. at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken) at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token) at Microsoft.AspNetCore.WebUtilities.FormPipeReader.ReadFormAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Http.Features.FormFeature.InnerReadFormAsync(CancellationToken cancellationToken) at Duende.IdentityServer.Validation.PostBodySecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/PostBodySecretParser.cs:line 60 at Duende.IdentityServer.Validation.SecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/SecretParser.cs:line 45 at Duende.IdentityServer.Validation.ClientSecretValidator.ValidateAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/ClientSecretValidator.cs:line 60 at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessTokenRequestAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 95 at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 81 at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in /_/src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 106 2025-07-12 22:16:01.869 +01:00 [ERR] Connection id "0HNDSHB92AIJU", Request id "0HNDSHB92AIJU:00000001": An unhandled exception was thrown by the application. Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content. at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken) at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token) at Microsoft.AspNetCore.WebUtilities.FormPipeReader.ReadFormAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Http.Features.FormFeature.InnerReadFormAsync(CancellationToken cancellationToken) at Duende.IdentityServer.Validation.PostBodySecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/PostBodySecretParser.cs:line 60 at Duende.IdentityServer.Validation.SecretParser.ParseAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/SecretParser.cs:line 45 at Duende.IdentityServer.Validation.ClientSecretValidator.ValidateAsync(HttpContext context) in /_/src/IdentityServer/Validation/Default/ClientSecretValidator.cs:line 60 at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessTokenRequestAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 95 at Duende.IdentityServer.Endpoints.TokenEndpoint.ProcessAsync(HttpContext context) in /_/src/IdentityServer/Endpoints/TokenEndpoint.cs:line 81 at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in /_/src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 106 at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IdentityServerOptions options, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in /_/src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 128 at Duende.IdentityServer.Hosting.MutualTlsEndpointMiddleware.Invoke(HttpContext context, IAuthenticationSchemeProvider schemes) in /_/src/IdentityServer/Hosting/MutualTlsEndpointMiddleware.cs:line 95 at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Duende.IdentityServer.Hosting.DynamicProviders.DynamicSchemeAuthenticationMiddleware.Invoke(HttpContext context) in /_/src/IdentityServer/Hosting/DynamicProviders/DynamicSchemes/DynamicSchemeAuthenticationMiddleware.cs:line 51 at Duende.IdentityServer.Hosting.BaseUrlMiddleware.Invoke(HttpContext context) in /_/src/IdentityServer/Hosting/BaseUrlMiddleware.cs:line 27 at Bit.Core.Utilities.CurrentContextMiddleware.Invoke(HttpContext httpContext, ICurrentContext currentContext, GlobalSettings globalSettings) in /source/src/Core/Utilities/CurrentContextMiddleware.cs:line 19 at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Builder.Extensions.UsePathBaseMiddleware.InvokeCore(HttpContext context, PathString matchedPath, PathString remainingPath) at Bit.Identity.Startup.<>c__DisplayClass10_1.<<Configure>b__2>d.MoveNext() in /source/src/Identity/Startup.cs:line 189 --- End of stack trace from previous location --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application) 2025-07-13 08:44:00.419 +01:00 [ERR] Unexpected end of request content. Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unexpected end of request content. at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1ContentLengthMessageBody.ReadAsyncInternal(CancellationToken cancellationToken) at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpRequestStream.ReadAsyncInternal(Memory`1 destination, CancellationToken cancellationToken) at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token) at System.Text.Json.Serialization.ReadBufferState.ReadFromStreamAsync(Stream utf8Json, CancellationToken cancellationToken, Boolean fillBuffer) at System.Text.Json.Serialization.Metadata.JsonTypeInfo`1.DeserializeAsync(Stream utf8Json, CancellationToken cancellationToken) at System.Text.Json.Serialization.Metadata.JsonTypeInfo`1.DeserializeAsObjectAsync(Stream utf8Json, CancellationToken cancellationToken) at Microsoft.AspNetCore.Mvc.Formatters.SystemTextJsonInputFormatter.ReadRequestBodyAsync(InputFormatterContext context, Encoding encoding) at Microsoft.AspNetCore.Mvc.Formatters.SystemTextJsonInputFormatter.ReadRequestBodyAsync(InputFormatterContext context, Encoding encoding) at Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BodyModelBinder.BindModelAsync(ModelBindingContext bindingContext) at Microsoft.AspNetCore.Mvc.ModelBinding.ParameterBinder.BindModelAsync(ActionContext actionContext, IModelBinder modelBinder, IValueProvider valueProvider, ParameterDescriptor parameter, ModelMetadata metadata, Object value, Object container) at Microsoft.AspNetCore.Mvc.Controllers.ControllerBinderDelegateProvider.<>c__DisplayClass0_0.<<CreateBinderDelegate>g__Bind|0>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean `isCompleted` ``` I would be interested to know if anyone following this thread and has the unexpected logout and biometrics reset problem and is NOT using an instance of the Bitwarden self hosted server. It might narrow the problem down to a server side issue or Android app issue.

GiteaMirror commented

@alexzeitgeist commented on GitHub (Jul 19, 2025):

At least in my case (still facing logouts): self hosted.

@alexzeitgeist commented on GitHub (Jul 19, 2025): At least in my case (still facing logouts): self hosted.

GiteaMirror commented

@alexzeitgeist commented on GitHub (Jul 27, 2025):

Fixed the license json file and so far so good with the latest android client - no sudden logouts detected after using it for over one week.

@alexzeitgeist commented on GitHub (Jul 27, 2025): Fixed the license json file and so far so good with the latest android client - no sudden logouts detected after using it for over one week.

GiteaMirror commented

@felmey commented on GitHub (Jul 27, 2025):

I also fixed the license JSON file (and then coincidentally had to do my annual renew and get a new license) and I haven't had any crashes in the latest Bitwarden app for two weeks. I think we figured out the issue. Although, I think the app could have more gracefully dealt with this issue and give the user some indication of the problem, it seems to be working fine now.

I'm ready to close this issue unless someone has a reason not to...

@felmey commented on GitHub (Jul 27, 2025): I also fixed the license JSON file (and then coincidentally had to do my annual renew and get a new license) and I haven't had any crashes in the latest Bitwarden app for two weeks. I think we figured out the issue. Although, I think the app could have more gracefully dealt with this issue and give the user some indication of the problem, it seems to be working fine now. I'm ready to close this issue unless someone has a reason not to...

GiteaMirror commented

@djpeck1 commented on GitHub (Jul 27, 2025):

I've had this issue since the beginning of the year. I was hoping that the license key issue would solve the problem for me also, but when I checked my license file there were no extra characters at the end of the key.

I have reverted back to using the 2024.10.0 version of the Android app and have had no issues since. Maybe the latest version of the Android app has finally resolved the problem so I will update to it and report back. Please keep the issue open for now.

@djpeck1 commented on GitHub (Jul 27, 2025): I've had this issue since the beginning of the year. I was hoping that the license key issue would solve the problem for me also, but when I checked my license file there were no extra characters at the end of the key. I have reverted back to using the 2024.10.0 version of the Android app and have had no issues since. Maybe the latest version of the Android app has finally resolved the problem so I will update to it and report back. Please keep the issue open for now.

GiteaMirror commented

@djpeck1 commented on GitHub (Jul 29, 2025):

I reinstalled the latest version of the Android app (2025.6.1) and for almost 2 days everything was fine.

This morning the app had logged me out and lost the biometric settings. It's really frustrating. So for me I'll have to revert back to the 2024.10.0 version of the app and try the latest version again in a few months, but I'm not holding much hope that this will get resolved.

@djpeck1 commented on GitHub (Jul 29, 2025): I reinstalled the latest version of the Android app (2025.6.1) and for almost 2 days everything was fine. This morning the app had logged me out and lost the biometric settings. It's really frustrating. So for me I'll have to revert back to the 2024.10.0 version of the app and try the latest version again in a few months, but I'm not holding much hope that this will get resolved.

GiteaMirror commented

@SaintPatrck commented on GitHub (Jul 29, 2025):

@djpeck1 we recently introduced a Flight Recorder feature to capture logs. If you're willing, could you turn it on and leave it running to capture logs when the logout occurs? Unfortunately, Flight Recorder is not enabled on self-hosted instances by default, so you will need to install a debug version and enable it manually in the Debug menu. This menu is reached by tapping three times with three fingers somewhere in the app, or by pressing SHIFT ~ if a keyboard is attached.

If the logout occurs while Flight Recorder is running it will capture the logout reason and we can investigate further.

For those encountering the unexpected characters in your license file; I've reported this to our server team, and they are investigating. I suggest opening an issue in the server repository with any more details that you feel may be helpful in their research.

@SaintPatrck commented on GitHub (Jul 29, 2025): @djpeck1 we recently introduced a Flight Recorder feature to capture logs. If you're willing, could you turn it on and leave it running to capture logs when the logout occurs? Unfortunately, Flight Recorder is not enabled on self-hosted instances by default, so you will need to install a debug version and enable it manually in the Debug menu. This menu is reached by tapping three times with three fingers somewhere in the app, or by pressing `SHIFT ~` if a keyboard is attached. If the logout occurs while Flight Recorder is running it will capture the logout reason and we can investigate further. For those encountering the unexpected characters in your license file; I've reported this to our server team, and they are investigating. I suggest opening an issue in the [server repository](https://github.com/bitwarden/server/) with any more details that you feel may be helpful in their research.

GiteaMirror commented

@djpeck1 commented on GitHub (Jul 30, 2025):

@SaintPatrck Thanks for your offer of help. I am willing to do whatever it takes to help resolve the issue.

If using Flight Recorder will help then let's do that. You mentioned that I will first have to install a debug version of the app. Please will you let me know where to download the debug version from?

Thanks again.

@djpeck1 commented on GitHub (Jul 30, 2025): @SaintPatrck Thanks for your offer of help. I am willing to do whatever it takes to help resolve the issue. If using Flight Recorder will help then let's do that. You mentioned that I will first have to install a debug version of the app. Please will you let me know where to download the debug version from? Thanks again.

GiteaMirror commented

@SaintPatrck commented on GitHub (Jul 30, 2025):

@djpeck1 I greatly appreciate your willingness to help out!

After double checking internally I realize the Flight Recorder feature is available in 2025.7.0 and 2025.7.1 for self-hosted users environments. You can enable the Flight Recorder from Settings > About. When enabled, you will be prompted to select a time-frame to leave it running. I suggest starting with 24 hours in hopes that the issue manifests quickly. There's also an option to leave the Flight Recorder enabled for 1 week if you prefer to leave it running. Once you have logs you can forward them to our CS team, referencing this GitHub issue, and we'll continue investigating.

If you're still interested in using a dev build, you can find it in the Password Manager 2025.7.1 (20513) release artifacts, com.x8bit.bitwarden.dev.apk.

@SaintPatrck commented on GitHub (Jul 30, 2025): @djpeck1 I greatly appreciate your willingness to help out! After double checking internally I realize the Flight Recorder feature is available in 2025.7.0 and 2025.7.1 for self-hosted users environments. You can enable the Flight Recorder from Settings > About. When enabled, you will be prompted to select a time-frame to leave it running. I suggest starting with 24 hours in hopes that the issue manifests quickly. There's also an option to leave the Flight Recorder enabled for 1 week if you prefer to leave it running. Once you have logs you can forward them to our CS team, referencing this GitHub issue, and we'll continue investigating. If you're still interested in using a dev build, you can find it in the [Password Manager 2025.7.1 (20513)](https://github.com/bitwarden/android/releases/tag/untagged-e73f3fed1526275b4183) release artifacts, [com.x8bit.bitwarden.dev.apk](https://github.com/bitwarden/android/releases/download/untagged-e73f3fed1526275b4183/com.x8bit.bitwarden.dev.apk).

GiteaMirror commented

2025-11-26 23:10:21 -06:00

@djpeck1 commented on GitHub (Jul 30, 2025):

@SaintPatrck I'm currently on version 2025.6.1 so to enable Flight Recorder I need to update to one of the Dev versions you mentioned.

The problem I'm having is that the links you gave me to the 2025.7.0 and 2025.7.1 versions just give me a 404 page not found error. Can you kindly check the links again so I can install one of the Dev versions. Thanks.

@djpeck1 commented on GitHub (Jul 30, 2025): @SaintPatrck I'm currently on version 2025.6.1 so to enable Flight Recorder I need to update to one of the Dev versions you mentioned. The problem I'm having is that the links you gave me to the 2025.7.0 and 2025.7.1 versions just give me a 404 page not found error. Can you kindly check the links again so I can install one of the Dev versions. Thanks.

GiteaMirror commented

@SaintPatrck commented on GitHub (Jul 30, 2025):

Interesting. Can you try these links for 2025.7.0?
https://github.com/bitwarden/android/releases/tag/v2025.7.0-bwpm
https://github.com/bitwarden/android/releases/download/v2025.7.0-bwpm/com.x8bit.bitwarden.dev.apk

@SaintPatrck commented on GitHub (Jul 30, 2025): Interesting. Can you try these links for 2025.7.0? https://github.com/bitwarden/android/releases/tag/v2025.7.0-bwpm https://github.com/bitwarden/android/releases/download/v2025.7.0-bwpm/com.x8bit.bitwarden.dev.apk

GiteaMirror commented

2025-11-26 23:10:21 -06:00

@djpeck1 commented on GitHub (Jul 30, 2025):

Thanks for that. Those links work just fine. I'll get the Dev app installed and get Flight Recorder turned on. The log out problem happens regularly so hopefully the logs will help identify the problem.

@djpeck1 commented on GitHub (Jul 30, 2025): Thanks for that. Those links work just fine. I'll get the Dev app installed and get Flight Recorder turned on. The log out problem happens regularly so hopefully the logs will help identify the problem.

GiteaMirror commented

2025-11-26 23:10:21 -06:00

@djpeck1 commented on GitHub (Aug 1, 2025):

@SaintPatrck I didn't have to wait long for the unexpected logout to happen. It was soon after I started using my phone the following morning. Flight Recorder logs were successfully captured and I have now raised a support request with Bitwarden customer service to have the issue investigated. I sent the logs in with the request.

I had a look through the logs myself for anything obvious and a few things stood out at the time of the issue;

2025-07-31_07:01:54:129 – DEBUG – BitwardenNetworkClient – <-- HTTP FAILED: java.net.SocketException: Software caused connection abort
2025-07-31 07:01:54:135 – WARNING – Network Error: https://api.bitwarden.com/connect/token
java.net.SocketException: Software caused connection abort

2025-07-31 07:01:54:157 – DEBUG – logout _reason=TokenRefreshFail

@djpeck1 commented on GitHub (Aug 1, 2025): @SaintPatrck I didn't have to wait long for the unexpected logout to happen. It was soon after I started using my phone the following morning. Flight Recorder logs were successfully captured and I have now raised a support request with Bitwarden customer service to have the issue investigated. I sent the logs in with the request. I had a look through the logs myself for anything obvious and a few things stood out at the time of the issue; 2025-07-31_07:01:54:129 – DEBUG – BitwardenNetworkClient – <-- HTTP FAILED: java.net.SocketException: Software caused connection abort 2025-07-31 07:01:54:135 – WARNING – Network Error: https://api.bitwarden.com/connect/token java.net.SocketException: Software caused connection abort 2025-07-31 07:01:54:157 – DEBUG – logout _reason=TokenRefreshFail

GiteaMirror commented

@djpeck1 commented on GitHub (Sep 5, 2025):

I'm now on version 2025.8.0 of the Android app and have been using it for two weeks now and no unexpected log outs or biometrics reset.

So for me at least the problem appears to be resolved now 🙂

@djpeck1 commented on GitHub (Sep 5, 2025): I'm now on version 2025.8.0 of the Android app and have been using it for two weeks now and no unexpected log outs or biometrics reset. So for me at least the problem appears to be resolved now 🙂

GiteaMirror commented

@alexzeitgeist commented on GitHub (Sep 5, 2025):

The logout issue has been resolved for me, whether by fixing the malformed .json file or by updating to one of the more recent clients.

@alexzeitgeist commented on GitHub (Sep 5, 2025): The logout issue has been resolved for me, whether by fixing the malformed .json file or by updating to one of the more recent clients.

GiteaMirror commented

@ajeetdsouza commented on GitHub (Oct 26, 2025):

I'm on v2025.10.0 and I'm still facing this issue with bitwarden.com (aka not self hosted).

@ajeetdsouza commented on GitHub (Oct 26, 2025): I'm on v2025.10.0 and I'm still facing this issue with bitwarden.com (aka not self hosted).

GiteaMirror commented