[GH-ISSUE #6694] [PM-33902] Passkey Retrieval hangs on Firefox on Android #39456

New Issue

GiteaMirror · 2026-04-23T18:22:20-05:00

GiteaMirror commented

2026-04-23 18:22:20 -05:00

Originally created by @josephlr on GitHub (Mar 19, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6694

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.

Originally created by @josephlr on GitHub (Mar 19, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6694 ### Origin Web (Browser) ### Web URL or App name passkeys.io, github.com, healthequity.com ### Passkey Action - [ ] Creating new passkey (Registration) - [x] 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 - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

GiteaMirror added the bug-passkey app:password-manager labels 2026-04-23 18:22:20 -05:00

GiteaMirror closed this issue

2026-04-23 18:22:21 -05:00

GiteaMirror commented

2026-04-23 18:22:22 -05:00

@bitwarden-bot commented on GitHub (Mar 19, 2026):

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

@bitwarden-bot commented on GitHub (Mar 19, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-33902](https://bitwarden.atlassian.net/browse/PM-33902) [PM-33902]: https://bitwarden.atlassian.net/browse/PM-33902?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

GiteaMirror commented

2026-04-23 18:22:23 -05:00

@pamperer562580892423 commented on GitHub (Mar 19, 2026):

Another user here. - And three things:

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.
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.
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.

@pamperer562580892423 commented on GitHub (Mar 19, 2026): 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.

GiteaMirror commented

2026-04-23 18:22:23 -05:00

@josephlr commented on GitHub (Mar 19, 2026):

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)

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

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.

@josephlr commented on GitHub (Mar 19, 2026): > 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.

GiteaMirror commented

2026-04-23 18:22:24 -05:00

@pamperer562580892423 commented on GitHub (Mar 19, 2026):

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).

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:

Version: 2026.2.1 (21297)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2026.2-rc47@6902c19c0093fa476bbf74ccaa70c9f14afbb82f
💻 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

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:

@pamperer562580892423 commented on GitHub (Mar 19, 2026): > > 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: bitwarden/android/release/2026.2-rc47@6902c19c0093fa476bbf74ccaa70c9f14afbb82f 💻 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: <img width="400" height="454" alt="Image" src="https://github.com/user-attachments/assets/063e43f8-9fdf-45f0-9a0d-5f8177e0cd90" />

GiteaMirror commented

2026-04-23 18:22:25 -05:00

@SaintPatrck commented on GitHub (Mar 20, 2026):

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.

@SaintPatrck commented on GitHub (Mar 20, 2026): 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](https://github.com/bitwarden/android/blob/main/app/src/main/kotlin/com/x8bit/bitwarden/data/credentials/processor/CredentialProviderProcessorImpl.kt#L95) 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.

GiteaMirror commented

2026-04-23 18:22:26 -05:00

@pamperer562580892423 commented on GitHub (Mar 21, 2026):

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

@pamperer562580892423 commented on GitHub (Mar 21, 2026): @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](https://github.com/bitwarden/android/issues/6440) 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"](https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941#p-199071-h-22-optional-enable-google-or-another-service-as-an-additional-service-5) 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](https://bitwarden.com/help/auto-fill-android/#autofill-methods)? --> 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](https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941#p-199071-h-32-choose-how-autofill-suggestions-should-be-displayed-8) 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)

GiteaMirror commented

2026-04-23 18:22:27 -05:00

@zeropoint46 commented on GitHub (Mar 22, 2026):

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.

@zeropoint46 commented on GitHub (Mar 22, 2026): 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.

GiteaMirror commented

2026-04-23 18:22:27 -05:00

@indiana11011100 commented on GitHub (Mar 22, 2026):

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: bitwarden/android/release/2026.3-rc48@d8a9c596b27c9a68b63304d49784117bbebc6683
💻 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:

@indiana11011100 commented on GitHub (Mar 22, 2026): 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: bitwarden/android/release/2026.3-rc48@d8a9c596b27c9a68b63304d49784117bbebc6683 💻 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: <img width="572" height="1200" alt="Image" src="https://github.com/user-attachments/assets/2f5fa7db-3ba7-45fb-8814-9812e4b5abe0" /> Same issue if I try to login on my private Authentik instance via PWA or directly in Firefox. PC working: <img width="423" height="325" alt="Image" src="https://github.com/user-attachments/assets/7ef7b40c-c944-41e7-bb3b-37a78448f154" /> Mobile Firefox Version: <img width="524" height="540" alt="Image" src="https://github.com/user-attachments/assets/6c7412cf-0801-4625-aa48-c01029d1f2d1" />

GiteaMirror commented

2026-04-23 18:22:28 -05:00

@pamperer562580892423 commented on GitHub (Mar 22, 2026):

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

@pamperer562580892423 commented on GitHub (Mar 22, 2026): @zeropoint46 @indiana11011100 Did you check for the things mentioned above? (including providing additional data via the [Flight Recorder](https://bitwarden.com/help/flight-recorder/#using-flight-recorder)?) @zeropoint46 Are you also on Android 16?

GiteaMirror commented

2026-04-23 18:22:29 -05:00

@indiana11011100 commented on GitHub (Mar 22, 2026):

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

Open PWA App
Try login via Authentik
Inline Password disapeared first time
2nd try user and password worked
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.

@indiana11011100 commented on GitHub (Mar 22, 2026): @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.

GiteaMirror commented

2026-04-23 18:22:29 -05:00

@pamperer562580892423 commented on GitHub (Mar 22, 2026):

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...)

@pamperer562580892423 commented on GitHub (Mar 22, 2026): > 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...)

GiteaMirror commented

2026-04-23 18:22:30 -05:00

@indiana11011100 commented on GitHub (Mar 23, 2026):

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...)

Yeah official server or bitwarden lite would be nice, especially bw-lite not so long available right now.
Anyway, good that I still own another Pixel 8 which I've not used for longer time, so not fully up to date.
First, this Pixel with some older version of the App and with latest is working fine and maybe it will help.
Second I guess it is probably an issue with last Pixel Security update in combination with the BW App.
Finally I guess the log of Flight Recorder could collect more data?
Actually I see it is quite difficult to diagnose, but Vaultwarden should not be the cause.

Other Pixel 8:
Android 16
Security Update: 5.10.26
Play Systemupdate: 01.09.25
Build: BP3A.251005.004.B1

Before App Update:
© Bitwarden Inc. 2015-2026

Version: 2025.9.1 (20742)
📱 google Pixel 8 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2025.9-rc35@6f6aacabfbc803c44b52088889b46057df6801e2
💻 build source: bitwarden/android/actions/runs/17865058734/attempts/1
🦀 SDK: 1.0.0-3101-0eba924a
🌩 Server: Vaultwarden 2025.12.0

After App Update:
© Bitwarden Inc. 2015-2026

Version: 2026.3.0 (21345)
📱 google Pixel 8 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2026.3-rc48@d8a9c596b27c9a68b63304d49784117bbebc6683
💻 build source: bitwarden/android/actions/runs/23011287575/attempts/1
🦀 SDK: 2.0.0-5425-a6f4a233
🌩 Server: Vaultwarden 2025.12.0

Log old Version and login via PWA and Authentik (working):

Bitwarden Android
Log Start Time: 2026-03-23 22:07:01:871
Log Duration: 1h
App Version: 2025.9.1 (20742)
Build: release/standard
Operating System: 16 (36)
Device: google Pixel 8
Fingerprint: google/shiba/shiba:16/BP3A.251005.004.B1/14042072:user/release-keys
2026-03-23 22:07:01:875 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:07:01:876 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:07:01:931 – 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-23 22:07:04:541 – DEBUG – c – App is backgrounded
2026-03-23 22:07:22:114 – DEBUG – c – App is foregrounded
2026-03-23 22:07:22:135 – DEBUG – a – MainActivity destination changed: root
2026-03-23 22:07:22:161 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute
2026-03-23 22:07:22:189 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:07:22:192 – DEBUG – a – RootNavScreen destination changed: ip.m0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:07:23:281 – DEBUG – c – App is backgrounded
2026-03-23 22:07:28:589 – DEBUG – a – Parsing AssistStructure -- 678
2026-03-23 22:07:28:589 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 678
2026-03-23 22:07:28:608 – DEBUG – a – Autofill request isInlineEnabled=true -- 678
2026-03-23 22:07:28:609 – DEBUG – d – Autofill request constructing FilledData
2026-03-23 22:07:28:611 – DEBUG – c – Autofill request is Fillable -- 678
2026-03-23 22:07:28:686 – DEBUG – c – Autofill request constructing SaveInfo -- 678
2026-03-23 22:07:28:692 – DEBUG – c – Autofill request constructing FillResponse
2026-03-23 22:07:28:692 – DEBUG – c – Autofill request isInCompatMode=false -- 678
2026-03-23 22:07:28:706 – DEBUG – b – Autofill request isInlineCompatible=true
2026-03-23 22:07:28:714 – DEBUG – b – Autofill request isInlineCompatible=true
2026-03-23 22:07:28:714 – DEBUG – b – Autofill request isInlineCompatible=true
2026-03-23 22:07:28:715 – DEBUG – c – Autofill request success: Fillable -- 678
2026-03-23 22:07:46:125 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 680
2026-03-23 22:07:46:125 – DEBUG – a – Parsing AssistStructure -- 680
2026-03-23 22:07:46:132 – DEBUG – a – Autofill request isInlineEnabled=true -- 680
2026-03-23 22:07:46:133 – DEBUG – c – Autofill request is Fillable -- 680
2026-03-23 22:07:46:134 – DEBUG – d – Autofill request constructing FilledData
2026-03-23 22:07:46:181 – DEBUG – c – Autofill request isInCompatMode=false -- 680
2026-03-23 22:07:46:182 – DEBUG – c – Autofill request constructing FillResponse
2026-03-23 22:07:46:186 – DEBUG – b – Autofill request isInlineCompatible=true
2026-03-23 22:07:46:186 – DEBUG – b – Autofill request isInlineCompatible=true
2026-03-23 22:07:46:181 – DEBUG – c – Autofill request constructing SaveInfo -- 680
2026-03-23 22:07:46:186 – DEBUG – c – Autofill request success: Fillable -- 680
2026-03-23 22:07:55:761 – DEBUG – c – App is foregrounded
2026-03-23 22:07:55:780 – DEBUG – a – MainActivity destination changed: root
2026-03-23 22:07:55:807 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute
2026-03-23 22:07:55:834 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:07:55:836 – DEBUG – a – RootNavScreen destination changed: ip.m0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:07:56:879 – DEBUG – c – App is backgrounded
2026-03-23 22:08:07:162 – DEBUG – c – App is foregrounded
2026-03-23 22:08:09:704 – 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-23 22:08:11:216 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute

Log latest version and login via PWA and Authentik (working)

Bitwarden Android - Password Manager
Log Start Time: 2026-03-23 22:23:05:199
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/BP3A.251005.004.B1/14042072:user/release-keys
Bitwarden Android - Password Manager
Log Start Time: 2026-03-23 22:23:05:199
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/BP3A.251005.004.B1/14042072:user/release-keys
Bitwarden Android - Password Manager
Log Start Time: 2026-03-23 22:23:05:199
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/BP3A.251005.004.B1/14042072:user/release-keys
2026-03-23 22:23:05:204 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:23:05:204 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:23:05:239 – 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-23 22:23:07:461 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-03-23 22:23:26:117 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 688
2026-03-23 22:23:26:118 – DEBUG – a – Parsing AssistStructure -- 688
2026-03-23 22:23:26:125 – DEBUG – a – Autofill request isInlineEnabled=true -- 688
2026-03-23 22:23:26:126 – DEBUG – c – Autofill request constructing FilledData
2026-03-23 22:23:26:126 – DEBUG – c – Autofill request is Fillable -- 688
2026-03-23 22:23:26:229 – DEBUG – c – Autofill request constructing SaveInfo -- 688
2026-03-23 22:23:26:231 – DEBUG – c – Autofill request isInCompatMode=false -- 688
2026-03-23 22:23:26:232 – DEBUG – c – Autofill request constructing FillResponse
2026-03-23 22:23:26:239 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:26:245 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:26:249 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:26:252 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:26:252 – DEBUG – c – Autofill request success: Fillable -- 688
2026-03-23 22:23:31:429 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
2026-03-23 22:23:31:441 – DEBUG – q1 – Autofill -- Cipher found
2026-03-23 22:23:31:442 – DEBUG – a – Parsing AssistStructure -- null
2026-03-23 22:23:31:446 – DEBUG – a – Autofill request isInlineEnabled=true -- null
2026-03-23 22:23:31:459 – DEBUG – c – Autofill request constructing FilledData
2026-03-23 22:23:31:463 – DEBUG – q0 – Autofill success
2026-03-23 22:23:32:207 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-03-23 22:23:34:872 – DEBUG – BitwardenCredentialProviderService – Get credential request received.
2026-03-23 22:23:34:954 – DEBUG – m0 – Credentials retrieved.
2026-03-23 22:23:38:562 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
2026-03-23 22:23:38:605 – DEBUG – a – MainActivity destination changed: com.x8bit.bitwarden.ui.platform.feature.rootnav.RootNavigationRoute
2026-03-23 22:23:38:619 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute
2026-03-23 22:23:38:632 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:23:38:633 – DEBUG – a – RootNavScreen destination changed: jq.n0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-23 22:23:39:533 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded
2026-03-23 22:23:43:252 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 690
2026-03-23 22:23:43:252 – DEBUG – a – Parsing AssistStructure -- 690
2026-03-23 22:23:43:268 – DEBUG – c – Autofill request is Fillable -- 690
2026-03-23 22:23:43:268 – DEBUG – a – Autofill request isInlineEnabled=true -- 690
2026-03-23 22:23:43:271 – DEBUG – c – Autofill request constructing FilledData
2026-03-23 22:23:43:309 – DEBUG – c – Autofill request constructing SaveInfo -- 690
2026-03-23 22:23:43:310 – DEBUG – c – Autofill request constructing FillResponse
2026-03-23 22:23:43:311 – DEBUG – c – Autofill request isInCompatMode=false -- 690
2026-03-23 22:23:43:313 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:43:316 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:43:321 – DEBUG – c – Autofill request isInlineCompatible=true
2026-03-23 22:23:43:323 – DEBUG – c – Autofill request success: Fillable -- 690
2026-03-23 22:23:53:092 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded
2026-03-23 22:23:55:850 – DEBUG – f – Network status change: Wifi(strength=GOOD)

Edit 1:
Updated Firefox to 148.0.1 and latest Play Systemupdate (01.02.26), Passkeys still working.
Latest Android update has ~3GB and will take a while.

Edit 2:
Verfied (update has installed), the latest Android update 05.03.2026 or some version before crashes BW-Passkey prompt via Firefox.

@indiana11011100 commented on GitHub (Mar 23, 2026): > > 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...) Yeah official server or bitwarden lite would be nice, especially bw-lite not so long available right now. Anyway, good that I still own another Pixel 8 which I've not used for longer time, so not fully up to date. First, this Pixel with some older version of the App and with latest is working fine and maybe it will help. Second I guess it is probably an issue with last Pixel Security update in combination with the BW App. Finally I guess the log of Flight Recorder could collect more data? Actually I see it is quite difficult to diagnose, but Vaultwarden should not be the cause. <img width="495" height="1100" alt="Image" src="https://github.com/user-attachments/assets/0b7f2278-d516-4ecc-a43e-a9c275f5c382" /> <img width="517" height="600" alt="Image" src="https://github.com/user-attachments/assets/8124ea87-817c-4888-ab5b-34c2a5bb04c5" /> Other Pixel 8: Android 16 Security Update: 5.10.26 Play Systemupdate: 01.09.25 Build: BP3A.251005.004.B1 **Before App Update:** © Bitwarden Inc. 2015-2026 Version: 2025.9.1 (20742) 📱 google Pixel 8 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2025.9-rc35@6f6aacabfbc803c44b52088889b46057df6801e2 💻 build source: bitwarden/android/actions/runs/17865058734/attempts/1 🦀 SDK: 1.0.0-3101-0eba924a 🌩 Server: Vaultwarden 2025.12.0 **After App Update:** © Bitwarden Inc. 2015-2026 Version: 2026.3.0 (21345) 📱 google Pixel 8 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2026.3-rc48@d8a9c596b27c9a68b63304d49784117bbebc6683 💻 build source: bitwarden/android/actions/runs/23011287575/attempts/1 🦀 SDK: 2.0.0-5425-a6f4a233 🌩 Server: Vaultwarden 2025.12.0 Log old Version and login via PWA and Authentik (working): ``` Bitwarden Android Log Start Time: 2026-03-23 22:07:01:871 Log Duration: 1h App Version: 2025.9.1 (20742) Build: release/standard Operating System: 16 (36) Device: google Pixel 8 Fingerprint: google/shiba/shiba:16/BP3A.251005.004.B1/14042072:user/release-keys 2026-03-23 22:07:01:875 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:07:01:876 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:07:01:931 – 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-23 22:07:04:541 – DEBUG – c – App is backgrounded 2026-03-23 22:07:22:114 – DEBUG – c – App is foregrounded 2026-03-23 22:07:22:135 – DEBUG – a – MainActivity destination changed: root 2026-03-23 22:07:22:161 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2026-03-23 22:07:22:189 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:07:22:192 – DEBUG – a – RootNavScreen destination changed: ip.m0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:07:23:281 – DEBUG – c – App is backgrounded 2026-03-23 22:07:28:589 – DEBUG – a – Parsing AssistStructure -- 678 2026-03-23 22:07:28:589 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 678 2026-03-23 22:07:28:608 – DEBUG – a – Autofill request isInlineEnabled=true -- 678 2026-03-23 22:07:28:609 – DEBUG – d – Autofill request constructing FilledData 2026-03-23 22:07:28:611 – DEBUG – c – Autofill request is Fillable -- 678 2026-03-23 22:07:28:686 – DEBUG – c – Autofill request constructing SaveInfo -- 678 2026-03-23 22:07:28:692 – DEBUG – c – Autofill request constructing FillResponse 2026-03-23 22:07:28:692 – DEBUG – c – Autofill request isInCompatMode=false -- 678 2026-03-23 22:07:28:706 – DEBUG – b – Autofill request isInlineCompatible=true 2026-03-23 22:07:28:714 – DEBUG – b – Autofill request isInlineCompatible=true 2026-03-23 22:07:28:714 – DEBUG – b – Autofill request isInlineCompatible=true 2026-03-23 22:07:28:715 – DEBUG – c – Autofill request success: Fillable -- 678 2026-03-23 22:07:46:125 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 680 2026-03-23 22:07:46:125 – DEBUG – a – Parsing AssistStructure -- 680 2026-03-23 22:07:46:132 – DEBUG – a – Autofill request isInlineEnabled=true -- 680 2026-03-23 22:07:46:133 – DEBUG – c – Autofill request is Fillable -- 680 2026-03-23 22:07:46:134 – DEBUG – d – Autofill request constructing FilledData 2026-03-23 22:07:46:181 – DEBUG – c – Autofill request isInCompatMode=false -- 680 2026-03-23 22:07:46:182 – DEBUG – c – Autofill request constructing FillResponse 2026-03-23 22:07:46:186 – DEBUG – b – Autofill request isInlineCompatible=true 2026-03-23 22:07:46:186 – DEBUG – b – Autofill request isInlineCompatible=true 2026-03-23 22:07:46:181 – DEBUG – c – Autofill request constructing SaveInfo -- 680 2026-03-23 22:07:46:186 – DEBUG – c – Autofill request success: Fillable -- 680 2026-03-23 22:07:55:761 – DEBUG – c – App is foregrounded 2026-03-23 22:07:55:780 – DEBUG – a – MainActivity destination changed: root 2026-03-23 22:07:55:807 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2026-03-23 22:07:55:834 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:07:55:836 – DEBUG – a – RootNavScreen destination changed: ip.m0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:07:56:879 – DEBUG – c – App is backgrounded 2026-03-23 22:08:07:162 – DEBUG – c – App is foregrounded 2026-03-23 22:08:09:704 – 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-23 22:08:11:216 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute ``` Log latest version and login via PWA and Authentik (working) ``` Bitwarden Android - Password Manager Log Start Time: 2026-03-23 22:23:05:199 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/BP3A.251005.004.B1/14042072:user/release-keys Bitwarden Android - Password Manager Log Start Time: 2026-03-23 22:23:05:199 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/BP3A.251005.004.B1/14042072:user/release-keys Bitwarden Android - Password Manager Log Start Time: 2026-03-23 22:23:05:199 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/BP3A.251005.004.B1/14042072:user/release-keys 2026-03-23 22:23:05:204 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:23:05:204 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:23:05:239 – 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-23 22:23:07:461 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded 2026-03-23 22:23:26:117 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 688 2026-03-23 22:23:26:118 – DEBUG – a – Parsing AssistStructure -- 688 2026-03-23 22:23:26:125 – DEBUG – a – Autofill request isInlineEnabled=true -- 688 2026-03-23 22:23:26:126 – DEBUG – c – Autofill request constructing FilledData 2026-03-23 22:23:26:126 – DEBUG – c – Autofill request is Fillable -- 688 2026-03-23 22:23:26:229 – DEBUG – c – Autofill request constructing SaveInfo -- 688 2026-03-23 22:23:26:231 – DEBUG – c – Autofill request isInCompatMode=false -- 688 2026-03-23 22:23:26:232 – DEBUG – c – Autofill request constructing FillResponse 2026-03-23 22:23:26:239 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:26:245 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:26:249 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:26:252 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:26:252 – DEBUG – c – Autofill request success: Fillable -- 688 2026-03-23 22:23:31:429 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded 2026-03-23 22:23:31:441 – DEBUG – q1 – Autofill -- Cipher found 2026-03-23 22:23:31:442 – DEBUG – a – Parsing AssistStructure -- null 2026-03-23 22:23:31:446 – DEBUG – a – Autofill request isInlineEnabled=true -- null 2026-03-23 22:23:31:459 – DEBUG – c – Autofill request constructing FilledData 2026-03-23 22:23:31:463 – DEBUG – q0 – Autofill success 2026-03-23 22:23:32:207 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded 2026-03-23 22:23:34:872 – DEBUG – BitwardenCredentialProviderService – Get credential request received. 2026-03-23 22:23:34:954 – DEBUG – m0 – Credentials retrieved. 2026-03-23 22:23:38:562 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded 2026-03-23 22:23:38:605 – DEBUG – a – MainActivity destination changed: com.x8bit.bitwarden.ui.platform.feature.rootnav.RootNavigationRoute 2026-03-23 22:23:38:619 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2026-03-23 22:23:38:632 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:23:38:633 – DEBUG – a – RootNavScreen destination changed: jq.n0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-23 22:23:39:533 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is backgrounded 2026-03-23 22:23:43:252 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 690 2026-03-23 22:23:43:252 – DEBUG – a – Parsing AssistStructure -- 690 2026-03-23 22:23:43:268 – DEBUG – c – Autofill request is Fillable -- 690 2026-03-23 22:23:43:268 – DEBUG – a – Autofill request isInlineEnabled=true -- 690 2026-03-23 22:23:43:271 – DEBUG – c – Autofill request constructing FilledData 2026-03-23 22:23:43:309 – DEBUG – c – Autofill request constructing SaveInfo -- 690 2026-03-23 22:23:43:310 – DEBUG – c – Autofill request constructing FillResponse 2026-03-23 22:23:43:311 – DEBUG – c – Autofill request isInCompatMode=false -- 690 2026-03-23 22:23:43:313 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:43:316 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:43:321 – DEBUG – c – Autofill request isInlineCompatible=true 2026-03-23 22:23:43:323 – DEBUG – c – Autofill request success: Fillable -- 690 2026-03-23 22:23:53:092 – DEBUG – AppStateManagerImpl$AppForegroundObserver – App is foregrounded 2026-03-23 22:23:55:850 – DEBUG – f – Network status change: Wifi(strength=GOOD) ``` Edit 1: Updated Firefox to 148.0.1 and latest Play Systemupdate (01.02.26), Passkeys still working. Latest Android update has ~3GB and will take a while. Edit 2: Verfied (update has installed), the latest Android update 05.03.2026 or some version before crashes BW-Passkey prompt via Firefox.

GiteaMirror commented

2026-04-23 18:22:30 -05:00

@mxxcon commented on GitHub (Mar 24, 2026):

I'm also experiencing this problem. Firefox is the same version as above.

Version: 2026.2.1 (21297)
📱 google Pixel 9 Pro 🤖 16@36 📦 prod
🧱 commit: bitwarden/android/release/2026.2-rc47@6902c19c0093fa476bbf74ccaa70c9f14afbb82f
💻 build source: bitwarden/android/actions/runs/22503857145/attempts/1
🦀 SDK: 2.0.0-5210-4ffddfe5
🌩 Server: 2026.2.1 @ US

I have bitwarden and ms authenticator enabled for auto-fill.
None of the previous suggestions worked.

Here's flight recorder of me navigating to https://myaccount.google.com/security and then tapping on passkeys link. On website's passkey prompt Firefox is just waiting.

Bitwarden Android - Password Manager
Log Start Time: 2026-03-24 08:17:23:427
Log Duration: 1h
App Version: 2026.2.1 (21297)
Build: release/standard
Operating System: 16 (36)
Device: google Pixel 9 Pro
Fingerprint: google/caiman/caiman:16/CP1A.260305.018/14887507:user/release-keys
2026-03-24 08:17:23:433 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-24 08:17:23:433 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-24 08:17:23:433 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-03-24 08:17:23:471 – 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-24 08:17:27:432 – DEBUG – a – App is backgrounded
2026-03-24 08:17:52:618 – DEBUG – a – App is foregrounded
2026-03-24 08:17:53:716 – 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-24 08:17:53:716 – 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-24 08:17:53:716 – 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

@mxxcon commented on GitHub (Mar 24, 2026): I'm also experiencing this problem. Firefox is the same version as above. Version: 2026.2.1 (21297) 📱 google Pixel 9 Pro 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2026.2-rc47@6902c19c0093fa476bbf74ccaa70c9f14afbb82f 💻 build source: bitwarden/android/actions/runs/22503857145/attempts/1 🦀 SDK: 2.0.0-5210-4ffddfe5 🌩 Server: 2026.2.1 @ US I have bitwarden and ms authenticator enabled for auto-fill. None of the previous suggestions worked. Here's flight recorder of me navigating to https://myaccount.google.com/security and then tapping on passkeys link. On website's passkey prompt Firefox is just waiting. ``` Bitwarden Android - Password Manager Log Start Time: 2026-03-24 08:17:23:427 Log Duration: 1h App Version: 2026.2.1 (21297) Build: release/standard Operating System: 16 (36) Device: google Pixel 9 Pro Fingerprint: google/caiman/caiman:16/CP1A.260305.018/14887507:user/release-keys 2026-03-24 08:17:23:433 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-24 08:17:23:433 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-24 08:17:23:433 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-03-24 08:17:23:471 – 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-24 08:17:27:432 – DEBUG – a – App is backgrounded 2026-03-24 08:17:52:618 – DEBUG – a – App is foregrounded 2026-03-24 08:17:53:716 – 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-24 08:17:53:716 – 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-24 08:17:53:716 – 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 ```

GiteaMirror commented

2026-04-23 18:22:31 -05:00

@SaintPatrck commented on GitHub (Mar 24, 2026):

Hi all,

Thank you for providing the Flight Recorder logs. Unfortunately I do not see this log statement in the failed attempt logs, which would indicate Bitwarden received a passkey requests. This likely means there's a communication breakdown either between Firefox and the OS, or the OS and Bitwarden preventing us from receiving the requests. We will continue to monitor and investigate.

@SaintPatrck commented on GitHub (Mar 24, 2026): Hi all, Thank you for providing the Flight Recorder logs. Unfortunately I do not see [this log statement](https://github.com/bitwarden/android/blob/main/app/src/main/kotlin/com/x8bit/bitwarden/data/credentials/processor/CredentialProviderProcessorImpl.kt#L95) in the failed attempt logs, which would indicate Bitwarden received a passkey requests. This likely means there's a communication breakdown either between Firefox and the OS, or the OS and Bitwarden preventing us from receiving the requests. We will continue to monitor and investigate.

GiteaMirror commented

2026-04-23 18:22:32 -05:00

@Nerdtality commented on GitHub (Mar 24, 2026):

Bitwarden Passkeys confirmed not working on Android 16 with Firefox

@Nerdtality commented on GitHub (Mar 24, 2026): Bitwarden Passkeys confirmed not working on Android 16 with Firefox

GiteaMirror commented

2026-04-23 18:22:32 -05:00

@harryyoud commented on GitHub (Mar 26, 2026):

This looks like a Firefox issue (see https://bugzilla.mozilla.org/show_bug.cgi?id=2022389). Bug fix landing in Firefox for Android version 149 (which is in Play Store now). Can probably safely close this issue as resolved.

Working here on Firefox for Android v149. Previously not working on Firefox 148 since Android 16 March 2026 update.

@harryyoud commented on GitHub (Mar 26, 2026): This looks like a Firefox issue (see https://bugzilla.mozilla.org/show_bug.cgi?id=2022389). Bug fix landing in Firefox for Android version 149 (which is in Play Store now). Can probably safely close this issue as resolved. Working here on Firefox for Android v149. Previously not working on Firefox 148 since Android 16 March 2026 update.

GiteaMirror commented

2026-04-23 18:22:33 -05:00

@mxxcon commented on GitHub (Mar 26, 2026):

I just upgraded to 149 and it's working for me

@mxxcon commented on GitHub (Mar 26, 2026): I just upgraded to 149 and it's working for me

GiteaMirror commented

2026-04-23 18:22:33 -05:00

@indiana11011100 commented on GitHub (Mar 27, 2026):

Can confirm this too 😄

Silently received Firefox 149 and the chain works.
Thanks everyone for any effort in investigation!

@indiana11011100 commented on GitHub (Mar 27, 2026): Can confirm this too 😄 Silently received Firefox 149 and the chain works. Thanks everyone for any effort in investigation!

GiteaMirror commented

2026-04-23 18:22:34 -05:00

@SaintPatrck commented on GitHub (Apr 3, 2026):

Thanks for the update everyone. Glad to hear it's working with 149.

@SaintPatrck commented on GitHub (Apr 3, 2026): Thanks for the update everyone. Glad to hear it's working with 149.

Sign in to join this conversation.

Branches Tags

main

sdlc/sdk-update

renovate/lock-file-maintenance

renovate/sonarqube

renovate/fastlane-2.x

crowdin-pull

cron-sync-privileged-browsers/60-sync

agalles/fdroid-only

remove-retrofit-dependency

release/hotfix-v2026.4.1-bwpm

beta-for-qa

target-sdk-37

PM-33982/build-device-screen

new-item-types/PM-32806_passport

new-item-types/PM-32808_drivers-license

BWA-99/show-next-totp

BWA-99/add-preview-next-totp-code-setting

renovate/glidecompose

sync-min-sdk

release/2026.4-rc51

fix/security-sast-22741894-bvwj

related-origin-passkey-creation

release/2026.4-rc50

platform/android-breaking-change-detection

innovation-sprint-2026-send-folder

release/2026.3-rc49

PM-34193-vault-lockout

android-collections

llm/add-resolving-sdk-updates-skill

QA-1523/sanity-test-saucelabs

release/2026.3-rc48

PM-26577-app-links-support

PM-26896-autofill-fix

release/2026.2-rc47

pr-6572

release/2026.2-rc46

release/2026.1-rc45

PM-30644/added-logs-for-debug

PM-30644/quicktile-nav-not-showing-migration

minor-gradle-updates

release/2026.1-rc42

release/2026.1-rc44

release/2026.1-rc43

PM-28834/set-landscape-on-horizonos-devices

PM-28468/validate-and-navigate-to-vault-migration

PM-20026/force-ltr-passwords-and-codes

release/2025.12-rc41

cmcg/testCoverage

PM-29014/talkback-support-for-passwords

release/2025.12-rc40

BRE-1305/publish_test

accept-user-certs

autofill-permissions

release/2025.11-rc39

PM-22479/check-all-certificates-validate-asset-links

release/2025.10-rc38

agalles/android-latest

retro-agent

PM-27001/skip-account-selection-only-one-exists-cxp

release/2025.10-rc37

agalles/test-1118

release/2025.10-rc36

PM-20593-token-refresh

QA-1126b/adding-native-sanity-test

release/2025.9-rc35

pm-25933/sdk-update-password

release/2025.9-rc34

release/2025.8-rc33

agalles/20250821-release

debug-release-issues

pm-24249-allow-automated-prs-for-sdk-updates

release/2025.8-rc32

release/WORKFLOW-TEST-2025.8-rc28

agalles/20250807release

release/2025.07-rc25

release/hotfix-v2025.7.0-bwa

pm-23311/export-vault-policy-bypass

release/2025.07-rc24

authenticator-pm-sync-flags-issue

release/hotfix-v2025.6.0-bwpm

release/2025.06-rc21

agalles/automate-android-fastlane-patch

release/2025.05-rc20

release/2025.04-rc19

languages/basque

release/2025.03-rc19

update-readme

qrcode/feature

innovation/archive/pm-19153-archive-items

qrcode/2-ui-fields

qrcode/1-page

hold-on-biometric-prompt-alternative

release-notes-process

release/2025.02-rc16

bwa-monorepo

PM-8223/new-device-verification-ux-improvements

pm-18451/exempt-from-policies

test-bwa

release/2025.01-rc15

release/2025.01-rc14

release/2024.12-rc13

pm-16670/sync-leave-notice

821

PM-16695/backport-lean-more-new-device-verification

release/hotfix-v2024.11.7

release/2024.11-rc1

pm-11304/collection-add-item-button

PM-14241/disabling-logs-app-crash

poc/offline-editing

new-version-calc

pm-11649/expired-link-services

pm-6702/add-feature-flag

pm-6702/email-verification-feature

pm-9933/marketing-copy-update

pm-6702/registration-flows

update-templates

pm-6701/email-verification-selfhost-registration

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/android#39456