[PM-33902] Passkey Retrieval hangs on Firefox on Android

[josephlr]

Origin

Web (Browser)

Web URL or App name

passkeys.io, github.com, healthequity.com

Passkey Action

• Creating new passkey (Registration)
• Signing in (Authentication)

Build Information

Bitwarden Android App Version: 2026.2.1 (21297)
Android Version: 16 (Android Security Update 2026-03-05, Google Play System Update 2026-02-01)
Firefox Version: 148.0.2 (Build # 2016148295), 15542f265e9e

Additional Information

On any site which supports passkey logins, I do the following:

• Create a Bitwaren-stored passkey on Desktop Web
• Sync Vault on Desktop
• Sync Vault in Android App
• Attempt to login on Web on Android

On Chrome (or in a native app), passkey login works correctly. The Bitwarden system prompt comes up, and I am able to login with the passkey provided by the Bitwarden App (via Android's Credential Manager API). However, on Firefox, no prompt appears. Instead nothing happens, and Firefox just waits until the passkey request times out.

Debugging info:

• Bitwarden is selected as the "Preferred Service" in the Android "Passwords, passkeys & accounts" setting
• Reinstalling Firefox didn't change anything
• Removing all extensions from Firefox didn't change anything
• Firefox is set as the default web browser

I really want to recommend Bitwarden to folks trying to use passkeys everywhere. However, as a Google Employee, I don't want to seem like I'm recommending a solution that is Chrome-only on Android. All other platforms have worked great so far; thanks for the amazing work!

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

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

[pamperer562580892423]

Another user here. - And three things:

1. Please add some more details by copying & pasting the following into another post or your OP: in the BW app, go to Settings --> About --> Version.

2. I can't reproduce your issue. On my Android 15 phone (FP 5) with BW app 2026.2.1 - though I seldom use Firefox nowadays - I just tried to login with a passkey from the BW vault on Firefox mobile (148.0.2), and at least on passkeys.io, GitHub and community.bitwarden.com (the BW Community Forum), I have no issue using my passkeys to log in.

3. I would recommend to check also your settings/configuration with this community guide for autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941

PS:

Firefox is set as the default web browser

That shouldn't be necessary. For my test now from a few minutes ago, Firefox was not set as default browser on my Android phone.

[josephlr]

1. Please add some more details by copying & pasting the following into another post or your OP: in the BW app, go to Settings --> About --> Version.

This should already be in the above report: 2026.2.1 (21297)

2. I can't reproduce your issue. On my Android 15 phone (FP 5) with BW app 2026.2.1 - though I seldom use Firefox nowadays - I just tried to login with a passkey from the BW vault on Firefox mobile (148.0.2), and at least on passkeys.io, GitHub and community.bitwarden.com (the BW Community Forum), I have no issue using my passkeys to log in.

Are you using the Bitwarden Firefox Extension? I'm only using the native Android App because:

• That seems to be the supported Chrome workflow
• I wasn't able to login to Bitwarden in the Firefox Extension

3. I would recommend to check also your settings/configuration with this community guide for autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941

I've followed those steps, and the Chrome Autofill integration is enabled. Disabling it did not change the problem. Firefox still hangs in the same way.

Firefox is set as the default web browser

That shouldn't be necessary. For my test now from a few minutes ago, Firefox was not set as default browser on my Android phone.

That makes sense, the issue seems to be the communication between Firefox and Bitwarden.

[pamperer562580892423]

1. Please add some more details by copying & pasting the following into another post or your OP: in the BW app, go to Settings --> About --> Version.

This should already be in the above report: 2026.2.1 (21297)

Actually, it contains more information than that, e.g. also the used device, server version etc. to get more debug info. But it's up to you (unless BW asked for it explicitly).

 

2. I can't reproduce your issue. On my Android 15 phone (FP 5) with BW app 2026.2.1 - though I seldom use Firefox nowadays - I just tried to login with a passkey from the BW vault on Firefox mobile (148.0.2), and at least on passkeys.io, GitHub and community.bitwarden.com (the BW Community Forum), I have no issue using my passkeys to log in.

Are you using the Bitwarden Firefox Extension? I'm only using the native Android App because:

No, I don't use the browser extension on Firefox mobile (as it's not even a supported usage, see here: https://bitwarden.com/help/product-faqs/#q-does-bitwarden-manage-in-browser-browser-extensions-on-android-mobile).

I'm using the BW mobile app - here my full details:

© Bitwarden Inc. 2015-2026

Version: 2026.2.1 (21297)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: 6902c19
💻 build source: bitwarden/android/actions/runs/22503857145/attempts/1
🦀 SDK: 2.0.0-5210-4ffddfe5
🌩 Server: 2026.3.0 @ EU

 

• That seems to be the supported Chrome workflow
• I wasn't able to login to Bitwarden in the Firefox Extension

3. I would recommend to check also your settings/configuration with this community guide for autofill on Android: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941

I've followed those steps, and the Chrome Autofill integration is enabled. Disabling it did not change the problem. Firefox still hangs in the same way.

Honestly, the Chrome/Brave/Vivaldi Autofill integration would be my least concern here, as it shouldn't have any effect on Firefox at all. - Did you look through the whole post?

 

Firefox is set as the default web browser

That shouldn't be necessary. For my test now from a few minutes ago, Firefox was not set as default browser on my Android phone.

That makes sense, the issue seems to be the communication between Firefox and Bitwarden.

Yeah, and in my case, that works. Maybe I'm the only one on the planet - but my guess would be, it's something with your device/configuration/setup, because when it works on my device, with the same app versions, it at least can't be a general defect.

PS: My Firefox details:

[SaintPatrck]

Hi @josephlr,

As a baseline sanity check, can you enable Flight Recorder then attempt to sign in with a passkey? If Bitwarden is receiving the request from Firefox and the System you will see this line in the logs. If you don't see it, that means we're not receiving the request. If we do receive the request, there should be more logs that will help identify where it's stalling in Bitwarden.

[pamperer562580892423]

@SaintPatrck Ah, Sorry, I have to memorize the existence of the Flight Recorder...

@josephlr I thought a bit about it, and there are not that many options that could play a role here, but I think you could check:

• did you disable Google Password Manager on your phone? (if yes, try to enable and update it, if necessary) --> we saw e.g. in this other issue here, that it can have unintended side effects to disable Google Password Manager on Android
• did you choose Google Password Manager as an "additional service" in the Android Passwords/Passkey/Account settings? (actually, I think it that could be beneficial, e.g. for passkey prompts)
• did you choose "inline" or "popout" as your autofill method? --> 1. try if the the other option works, if only for testing; 2. if you chose "inline", make sure your keyboard supports showing inline suggestions then (though, I'm not sure if inline/popout options play any important role in passkey prompts)

If that doesn't change anything, I would tend to think it might be a new issue with Android 16 maybe?! (though, I'm not a developer -- and my only other data point now is: it works on my Android 15 device)

[zeropoint46]

Just wanted to say I have Firefox 148.0.2 on Android on a pixel 9 pro and I'm having the same issue. I know that's not much help, but I thought I'd at least chime in to say it's more than just OP.

[indiana11011100]

Hi everyone, since few days I also mentioned that I can't use Passkeys anymore. Autfill works absolutely fine only when there is a PWA or Firefox website where I have Passkeys it does not work anymore.

Bitwarden App is still the autofill App and for testing once deselected and selected again. No change.

Here is my setup:
Pixel 8
Android 16
Security Update: 05.03.2026
Play Systemupdate: 01.02.2026
Build: CP1A.260305.018

Bitwarden App (Copy press has much more information than on phone screen shown ... good to know if posted via PC 😉):
© Bitwarden Inc. 2015-2026

Version: 2026.3.0 (21345)
📱 google Pixel 8 🤖 16@36 📦 prod
🧱 commit: d8a9c59
💻 build source: bitwarden/android/actions/runs/23011287575/attempts/1
🦀 SDK: 2.0.0-5425-a6f4a233
🌩 Server: Vaultwarden 2025.12.0
^^After last Vaultwarden update Passkeys have been working. As written above, mentioned not working in the last few days.

Phone not working / asking for Passkey:

Same issue if I try to login on my private Authentik instance via PWA or directly in Firefox.

PC working:

Mobile Firefox Version:

[pamperer562580892423]

@zeropoint46 @indiana11011100 Did you check for the things mentioned above? (including providing additional data via the Flight Recorder?)

@zeropoint46 Are you also on Android 16?

[indiana11011100]

@pamperer562580892423 thanks for the description link of Flight Recorder really missed that one.

• switched default bitwarden -> google -> bitwarden | no difference
• no app disabled
• Google additionaly enabled or not | no difference
• Bitwarden inline or popup (gboard) | no difference

Log:

1. Open PWA App
2. Try login via Authentik
3. Inline Password disapeared first time
4. 2nd try user and password worked
5. Passkey wating endless
   Is Log entry 14:12:42:363 the passkey request?
   The Password was already filled in.
   Btw. my authentik instance is able to use passkey only. This is working on my iPad, was working on my Android and Firefox extension on PC is not able to do.

Bitwarden Android - Password Manager
Log Start Time: 2026-03-22 14:11:40:529
Log Duration: 1h
App Version: 2026.3.0 (21345)
Build: release/standard
Operating System: 16 (36)
Device: google Pixel 8
Fingerprint: google/shiba/shiba:16/CP1A.260305.018/14887507:user/release-keys
2026-03-22 14:11:40:532 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:533 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:532 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:11:40:580 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-03-22 14:11:42:291 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.vault.feature.vault.VaultRoute in com.x8bit.bitwarden.ui.vault.feature.vault.VaultGraphRoute
2026-03-22 14:11:43:695 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-03-22 14:11:51:479 – DEBUG – a – Parsing AssistStructure -- 162
2026-03-22 14:11:51:479 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 162
2026-03-22 14:11:51:483 – DEBUG – c – Autofill request is Fillable -- 162
2026-03-22 14:11:51:483 – DEBUG – c – Autofill request constructing FilledData
2026-03-22 14:11:51:484 – DEBUG – a – Autofill request isInlineEnabled=true -- 162
2026-03-22 14:11:51:517 – DEBUG – c – Autofill request constructing SaveInfo -- 162
2026-03-22 14:11:51:521 – DEBUG – c – Autofill request constructing FillResponse
2026-03-22 14:11:51:522 – DEBUG – c – Autofill request isInCompatMode=false -- 162
2026-03-22 14:11:51:525 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:11:51:534 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:11:51:536 – DEBUG – c – Autofill request success: Fillable -- 162
2026-03-22 14:11:51:537 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:00:861 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 164
2026-03-22 14:12:00:861 – DEBUG – a – Parsing AssistStructure -- 164
2026-03-22 14:12:00:879 – DEBUG – a – Autofill request isInlineEnabled=true -- 164
2026-03-22 14:12:00:879 – DEBUG – c – Autofill request is Fillable -- 164
2026-03-22 14:12:00:879 – DEBUG – c – Autofill request constructing FilledData
2026-03-22 14:12:00:969 – DEBUG – c – Autofill request constructing SaveInfo -- 164
2026-03-22 14:12:00:970 – DEBUG – c – Autofill request constructing FillResponse
2026-03-22 14:12:00:970 – DEBUG – c – Autofill request isInCompatMode=false -- 164
2026-03-22 14:12:00:980 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:00:985 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:00:988 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:00:990 – DEBUG – c – Autofill request success: Fillable -- 164
2026-03-22 14:12:00:990 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:22:404 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 166
2026-03-22 14:12:22:404 – DEBUG – a – Parsing AssistStructure -- 166
2026-03-22 14:12:22:431 – DEBUG – c – Autofill request constructing FilledData
2026-03-22 14:12:22:429 – DEBUG – c – Autofill request is Fillable -- 166
2026-03-22 14:12:22:427 – DEBUG – a – Autofill request isInlineEnabled=true -- 166
2026-03-22 14:12:22:518 – DEBUG – c – Autofill request constructing SaveInfo -- 166
2026-03-22 14:12:22:520 – DEBUG – c – Autofill request isInCompatMode=false -- 166
2026-03-22 14:12:22:519 – DEBUG – c – Autofill request constructing FillResponse
2026-03-22 14:12:22:533 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:22:541 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:22:545 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:22:549 – DEBUG – c – Autofill request success: Fillable -- 166
2026-03-22 14:12:22:548 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-22 14:12:27:494 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
2026-03-22 14:12:27:522 – DEBUG – a – Parsing AssistStructure -- null
2026-03-22 14:12:27:521 – DEBUG – q1 – Autofill -- Cipher found
2026-03-22 14:12:27:531 – DEBUG – a – Autofill request isInlineEnabled=true -- null
2026-03-22 14:12:27:532 – DEBUG – c – Autofill request constructing FilledData
2026-03-22 14:12:27:533 – DEBUG – q0 – Autofill success
2026-03-22 14:12:28:253 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-03-22 14:12:42:355 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 168
2026-03-22 14:12:42:359 – DEBUG – a – Parsing AssistStructure -- 168
2026-03-22 14:12:42:363 – DEBUG – c – Autofill request success: Unfillable -- 168
2026-03-22 14:12:57:457 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
2026-03-22 14:13:01:091 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-03-22 14:13:01:093 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-03-22 14:13:01:093 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-03-22 14:13:04:545 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:545 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:545 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:546 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:546 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:547 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:548 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:548 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:04:548 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.flightrecorder.recordedLogs.RecordedLogsRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:11:662 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-03-22 14:13:24:037 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
2026-03-22 14:13:25:765 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:765 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:766 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:766 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:766 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:766 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:765 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:767 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:767 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-22 14:13:25:823 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute

Hope I didn't miss anything else.

[pamperer562580892423]

Hope I didn't miss anything else.

Honestly - though maybe this is a pure client-side issue?! - on GitHub's BW repositories, it's always best to report things with official Bitwarden servers, so that everyone can be sure, the unofficial server doesn't interact somehow with an issue. (generally spoken...)