github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-16 15:09:35 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #6443] [PM-31448] Passkey login returns "App not supported" #8475

New Issue
Closed
opened 2026-04-11 01:48:17 -05:00 by GiteaMirror · 36 comments
GiteaMirror commented 2026-04-11 01:48:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @wheremygit on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6443

Steps To Reproduce

  1. Go to Any website or app with passkey login.
  2. Choose passkey and authenticate

Expected Result

Should be able to login normally.

Actual Result

  1. Bitwarden returns "App not supported" on browsers (Both Firefox and Chromium). I tried it on Fennec and Cromite.
  2. For other apps it doesn't give any error but login doesn't happen. (Tried it on PayPal and Amazon India Apps)

Downgrading to 2025.12.1 fixed the issue.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.1.0

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden v1.35.2

Environment Details

  • Device: Xiaomi Redmi Note 8 Pro
  • OS: Lineage OS 22 based on Android 15
  • Tried the both F-Droid and APK versions of the Bitwarden App.

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 @wheremygit on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6443 ### Steps To Reproduce 1. Go to Any website or app with passkey login. 2. Choose passkey and authenticate ### Expected Result Should be able to login normally. ### Actual Result 1. Bitwarden returns "App not supported" on browsers (Both Firefox and Chromium). I tried it on Fennec and Cromite. 2. For other apps it doesn't give any error but login doesn't happen. (Tried it on PayPal and Amazon India Apps) Downgrading to 2025.12.1 fixed the issue. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 2026.1.0 ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden v1.35.2 ### Environment Details - Device: Xiaomi Redmi Note 8 Pro - OS: Lineage OS 22 based on Android 15 - Tried the both F-Droid and APK versions of the Bitwarden App. ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:password-managerbug labels 2026-04-11 01:48:17 -05:00
GiteaMirror commented 2026-04-11 01:48:19 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Jan 30, 2026):

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

<!-- gh-comment-id:3821836579 --> @bitwarden-bot commented on GitHub (Jan 30, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31448](https://bitwarden.atlassian.net/browse/PM-31448) [PM-31448]: https://bitwarden.atlassian.net/browse/PM-31448?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-11 01:48:20 -05:00
Author
Owner
Copy Link
Copy Source

@rmcdowell-bitwarden commented on GitHub (Jan 30, 2026):

Hello,

It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization.  The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here:
https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch

Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here:
https://bitwarden.com/help/install-on-premise-linux/
https://bitwarden.com/help/install-and-deploy-offline/

If you would like to know more about a Bitwarden self-hosted setup, I will happily put you in touch with our Sales Team, who will be able to provide you with a trial license.  You can also initiate this yourself here:
https://bitwarden.com/help/enterprise-free-trial/

This issue will now be closed.

<!-- gh-comment-id:3822097284 --> @rmcdowell-bitwarden commented on GitHub (Jan 30, 2026): Hello, It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization.  The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here: https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here: https://bitwarden.com/help/install-on-premise-linux/ https://bitwarden.com/help/install-and-deploy-offline/ If you would like to know more about a Bitwarden self-hosted setup, I will happily put you in touch with our Sales Team, who will be able to provide you with a trial license.  You can also initiate this yourself here: https://bitwarden.com/help/enterprise-free-trial/ This issue will now be closed.
GiteaMirror commented 2026-04-11 01:48:20 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 30, 2026):

The issue is not with Vaultwarden but the Bitwarden Android App itself. The iOS app is on the same version (2026.1.0) but passkeys work flawlessly on Bitwarden iOS with the same Vaultwarden setup.

<!-- gh-comment-id:3822110582 --> @wheremygit commented on GitHub (Jan 30, 2026): The issue is not with Vaultwarden but the Bitwarden Android App itself. The iOS app is on the same version (2026.1.0) but passkeys work flawlessly on Bitwarden iOS with the same Vaultwarden setup.
GiteaMirror commented 2026-04-11 01:48:21 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

Another user here.

The issue is not with Vaultwarden but the Bitwarden Android App itself.

You only would know that, if you tried to reproduce your issue with an official BW server software (self-hosted or cloud account). Vaultwarden recommends that before reporting issues to Bitwarden: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting

<!-- gh-comment-id:3824239041 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): Another user here. > The issue is not with Vaultwarden but the Bitwarden Android App itself. You only would know that, if you tried to reproduce your issue with an official BW server software (self-hosted or cloud account). Vaultwarden recommends that before reporting issues to Bitwarden: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting
GiteaMirror commented 2026-04-11 01:48:22 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 30, 2026):

You only would know that, if you tried to reproduce your issue with an official BW server

Same issue on a test account I created rn on bitwarden.com

Image
<!-- gh-comment-id:3824322553 --> @wheremygit commented on GitHub (Jan 30, 2026): > You only would know that, if you tried to reproduce your issue with an official BW server Same issue on a test account I created rn on bitwarden.com <img width="1080" height="2340" alt="Image" src="https://github.com/user-attachments/assets/23f4d318-c0cf-4837-b797-49dba1fe31e0" />
GiteaMirror commented 2026-04-11 01:48:22 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

@wheremygit I see the flight mode icon in your screenshot - were you offline when trying it?

Ah, and passkeys.io was a bit problematic in itself... (GitHub or the Bitwarden Community Forum produced more reliable results regarding passkey login in the past)

But I just tried passkeys.io with my own Android 15 phone (and BW mobile app 2026.1.0) again. I can create a passkey / store it in my vault, and can log in with it. And apart from that, I can use passkeys also in other situations via the BW mobile app.

So, I personally would think, the issue might be your phone / OS on the phone and/or settings/configuration.

<!-- gh-comment-id:3824415606 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): @wheremygit I see the flight mode icon in your screenshot - were you offline when trying it? Ah, and passkeys.io was a bit problematic in itself... (GitHub or the [Bitwarden Community Forum](https://community.bitwarden.com) produced more reliable results regarding passkey login in the past) But I just tried passkeys.io with my own Android 15 phone (and BW mobile app 2026.1.0) again. I can create a passkey / store it in my vault, and can log in with it. And apart from that, I can use passkeys also in other situations via the BW mobile app. So, I personally would think, the issue might be your phone / OS on the phone and/or settings/configuration.
GiteaMirror commented 2026-04-11 01:48:23 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 30, 2026):

were you offline when trying it?

Ummm no? I have a Wifi icon as well. How would I be able to access passkeys.io then?

issue might be your phone / OS on the phone and/or settings/configuration.

Again, the functionality works perfectly fine on 2025.12.1. I upgraded and downgraded multiple times and 2026.1.0 android app is giving this error. Tried 2026.1.0 on iOS as well it works perfectly fine over there. Tried on Bitwarden official server and Self-hosted Vaultwarden. Both are giving same issue. Tried with F-Droid version and Google Play APK.

So the issue lies with Android app version 2026.1.0 which is the only reasonable conclusion I can come up with.

<!-- gh-comment-id:3824595860 --> @wheremygit commented on GitHub (Jan 30, 2026): > were you offline when trying it? Ummm no? I have a Wifi icon as well. How would I be able to access passkeys.io then? > issue might be your phone / OS on the phone and/or settings/configuration. Again, the functionality works perfectly fine on 2025.12.1. I upgraded and downgraded multiple times and 2026.1.0 android app is giving this error. Tried 2026.1.0 on iOS as well it works perfectly fine over there. Tried on Bitwarden official server and Self-hosted Vaultwarden. Both are giving same issue. Tried with F-Droid version and Google Play APK. So the issue lies with Android app version 2026.1.0 which is the only reasonable conclusion I can come up with.
GiteaMirror commented 2026-04-11 01:48:23 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

issue might be your phone / OS on the phone and/or settings/configuration.

Again, the functionality works perfectly fine on 2025.12.1. I upgraded and downgraded multiple times and 2026.1.0 android app is giving this error. Tried 2026.1.0 on iOS as well it works perfectly fine over there. Tried on Bitwarden official server and Self-hosted Vaultwarden. Both are giving same issue. Tried with F-Droid version and Google Play APK.

So the issue lies with Android app version 2026.1.0 which is the only reasonable conclusion I can come up with.

I think I perfectly understand your reasoning here.

The only thing that remains without any good explanation: why does it work on my Android phone with 2026.1.0 (and probably on many others as well)? - And that could be an issue with your phone - maybe even a device-specific bug.

<!-- gh-comment-id:3824637152 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): > > issue might be your phone / OS on the phone and/or settings/configuration. > > Again, the functionality works perfectly fine on 2025.12.1. I upgraded and downgraded multiple times and 2026.1.0 android app is giving this error. Tried 2026.1.0 on iOS as well it works perfectly fine over there. Tried on Bitwarden official server and Self-hosted Vaultwarden. Both are giving same issue. Tried with F-Droid version and Google Play APK. > > So the issue lies with Android app version 2026.1.0 which is the only reasonable conclusion I can come up with. I think I perfectly understand your reasoning here. The only thing that remains without any good explanation: why does it work on my **Android** phone with 2026.1.0 (and probably on many others as well)? - And that _could_ be an issue with your phone - maybe even a device-specific bug.
GiteaMirror commented 2026-04-11 01:48:24 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 30, 2026):

why does it work on my Android phone with 2026.1.0

IDK and I don't have another Android to test

And that could be an issue with your phone - maybe even a device-specific bug.

My phone has stopped receiving updates since 2024 so there wasn't any systen update that could break things. KeepassDX works perfectly fine and BW 2025.12.1 worked too so it rules out any system misconfiguration as well. it could be device related but that will be upto the BW team to figure out. I have the logs file below when I tried to save a passkey.

flight_recorder_2026-01-31_00-51-28.txt

<!-- gh-comment-id:3825443005 --> @wheremygit commented on GitHub (Jan 30, 2026): > why does it work on my Android phone with 2026.1.0 IDK and I don't have another Android to test > And that could be an issue with your phone - maybe even a device-specific bug. My phone has stopped receiving updates since 2024 so there wasn't any systen update that could break things. KeepassDX works perfectly fine and BW 2025.12.1 worked too so it rules out any system misconfiguration as well. it could be device related but that will be upto the BW team to figure out. I have the logs file below when I tried to save a passkey. [flight_recorder_2026-01-31_00-51-28.txt](https://github.com/user-attachments/files/24973155/flight_recorder_2026-01-31_00-51-28.txt)
GiteaMirror commented 2026-04-11 01:48:25 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 30, 2026):

it could be device related but that will be upto the BW team to figure out.

True, but FYI: as this issue here is already closed, it's not very likely that anyone will look into it now. (Exceptions may always be possible - and in some cases issues can get re-opened - but I wouldn't count on it.)

<!-- gh-comment-id:3825575141 --> @pamperer562580892423 commented on GitHub (Jan 30, 2026): > it could be device related but that will be upto the BW team to figure out. True, but FYI: as this issue here is already closed, it's not very likely that anyone will look into it now. (Exceptions may always be possible - and in some cases issues can get re-opened - but I wouldn't count on it.)
GiteaMirror commented 2026-04-11 01:48:25 -05:00
Author
Owner
Copy Link
Copy Source

@UjuiUjuMandan commented on GitHub (Jan 31, 2026):

@rmcdowell-bitwarden let's say this is not related to vaultwarden. I'm using bitwarden.com and have the same problem here.

Device: Google Pixel 7a
OS: CalyxOS 6.10.20 based on Android 15

Tried with both https://passkeys.io and https://webauthn.io/ on Cromite and Fennec which are both included in the privileged list.

<!-- gh-comment-id:3828682292 --> @UjuiUjuMandan commented on GitHub (Jan 31, 2026): @rmcdowell-bitwarden let's say this is not related to vaultwarden. I'm using bitwarden.com and have the same problem here. Device: Google Pixel 7a OS: CalyxOS 6.10.20 based on Android 15 Tried with both https://passkeys.io and https://webauthn.io/ on Cromite and Fennec which are both included in the [privileged list](https://github.com/bitwarden/android/blob/v2026.1.0-bwpm/app/src/main/assets/fido2_privileged_community.json).
GiteaMirror commented 2026-04-11 01:48:26 -05:00
Author
Owner
Copy Link
Copy Source

@UjuiUjuMandan commented on GitHub (Jan 31, 2026):

why does it work on my Android phone with 2026.1.0

Android 15 with or without Google services? Stock or custom ROM? Both the reported LineageOS and CalyxOS require bootloader unlocking and are degoogled.

<!-- gh-comment-id:3828745362 --> @UjuiUjuMandan commented on GitHub (Jan 31, 2026): > why does it work on my Android phone with 2026.1.0 Android 15 with or without Google services? Stock or custom ROM? Both the reported LineageOS and CalyxOS require bootloader unlocking and are degoogled.
GiteaMirror commented 2026-04-11 01:48:26 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 31, 2026):

why does it work on my Android phone with 2026.1.0

Android 15 with or without Google services? Stock or custom ROM? Both the reported LineageOS and CalyxOS require bootloader unlocking and are degoogled.

@UjuiUjuMandan That quote was from me, but I'm not sure if you meant me... but in my case it's Fairphone 5, Stock ROM Android 15. -- I know at least LineageOS well enough to know, that it comes by default without Google services, but they can be installed before the first start of the system (don't remember the package name right now).

But good point: using passkeys on an Android phone still needs e.g. "Google Password Manager" (and/or "Android Credential Manager") as it "mediates" (as the platform-passkey-provider) also third-party passkey providers like the Bitwarden app. (though I don't exactly know the situation for all custom ROMs and which solution they have... if they have a solution for this)

<!-- gh-comment-id:3828756324 --> @pamperer562580892423 commented on GitHub (Jan 31, 2026): > > why does it work on my Android phone with 2026.1.0 > > Android 15 with or without Google services? Stock or custom ROM? Both the reported LineageOS and CalyxOS require bootloader unlocking and are degoogled. @UjuiUjuMandan That quote was from me, but I'm not sure if you meant me... but in my case it's Fairphone 5, Stock ROM Android 15. -- I know at least LineageOS well enough to know, that it comes by default without Google services, but they can be installed before the first start of the system (don't remember the package name right now). But good point: using passkeys on an Android phone still needs e.g. "Google Password Manager" (and/or "Android Credential Manager") as it "mediates" (as the platform-passkey-provider) also third-party passkey providers like the Bitwarden app. (though I don't exactly know the situation for all custom ROMs and which solution they have... if they have a solution for this)
GiteaMirror commented 2026-04-11 01:48:27 -05:00
Author
Owner
Copy Link
Copy Source

@UjuiUjuMandan commented on GitHub (Jan 31, 2026):

using passkeys on an Android phone still needs e.g. "Google Password Manager" (and/or "Android Credential Manager") as it "mediates" (as the platform-passkey-provider) also third-party passkey providers like the Bitwarden app.

Yes.

in my case it's Fairphone 5, Stock ROM Android 15

I suppose stock ROM shipped with Google Play Service.

@wheremygit Can you check if you have microG or Google Play Service installed?

<!-- gh-comment-id:3828782711 --> @UjuiUjuMandan commented on GitHub (Jan 31, 2026): > using passkeys on an Android phone still needs e.g. "Google Password Manager" (and/or "Android Credential Manager") as it "mediates" (as the platform-passkey-provider) also third-party passkey providers like the Bitwarden app. Yes. > in my case it's Fairphone 5, Stock ROM Android 15 I suppose stock ROM shipped with Google Play Service. @wheremygit Can you check if you have microG or Google Play Service installed?
GiteaMirror commented 2026-04-11 01:48:28 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Jan 31, 2026):

in my case it's Fairphone 5, Stock ROM Android 15

I suppose stock ROM shipped with Google Play Service.

@UjuiUjuMandan Yep. And I have no problem using passkeys with the BW mobile app. (well, apart from those services / Relying Parties, that have quirky passkey implementations that cause problems for others, too)

<!-- gh-comment-id:3828824693 --> @pamperer562580892423 commented on GitHub (Jan 31, 2026): > > in my case it's Fairphone 5, Stock ROM Android 15 > > I suppose stock ROM shipped with Google Play Service. @UjuiUjuMandan Yep. And I have no problem using passkeys with the BW mobile app. (well, apart from those services / Relying Parties, that have quirky passkey implementations that cause problems for others, too)
GiteaMirror commented 2026-04-11 01:48:28 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 31, 2026):

@wheremygit Can you check if you have microG or Google Play Service installed?

@UjuiUjuMandan Yep I do have Google Play Services Installed.

Edit: I also tried 2026.1.0 on my mom’s pixel 9 with Stock Android 16. It works fine over there.

<!-- gh-comment-id:3829031143 --> @wheremygit commented on GitHub (Jan 31, 2026): > @wheremygit Can you check if you have microG or Google Play Service installed? @UjuiUjuMandan Yep I do have Google Play Services Installed. Edit: I also tried 2026.1.0 on my mom’s pixel 9 with Stock Android 16. It works fine over there.
GiteaMirror commented 2026-04-11 01:48:29 -05:00
Author
Owner
Copy Link
Copy Source

@UjuiUjuMandan commented on GitHub (Jan 31, 2026):

Yep I do have Google Play Services Installed.

Oh, in that case I have no idea what went wrong. Before I supposed Bitwarden 2026.1.0 breaks microG's unofficial implemention only.

<!-- gh-comment-id:3829036895 --> @UjuiUjuMandan commented on GitHub (Jan 31, 2026): > Yep I do have Google Play Services Installed. Oh, in that case I have no idea what went wrong. Before I supposed Bitwarden 2026.1.0 breaks microG's unofficial implemention only.
GiteaMirror commented 2026-04-11 01:48:31 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 31, 2026):

@UjuiUjuMandan It could be because of custom ROMs maybe my gues.

<!-- gh-comment-id:3829043405 --> @wheremygit commented on GitHub (Jan 31, 2026): @UjuiUjuMandan It could be because of custom ROMs maybe my gues.
GiteaMirror commented 2026-04-11 01:48:33 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Jan 31, 2026):

Also I don’t think this has anything to do with microG or Play Services. Earlier I was using passkeys on Android 15 LineageOS w/o any MicroG or Google Play Services Installed.

<!-- gh-comment-id:3829059127 --> @wheremygit commented on GitHub (Jan 31, 2026): Also I don’t think this has anything to do with microG or Play Services. Earlier I was using passkeys on Android 15 LineageOS w/o any MicroG or Google Play Services Installed.
GiteaMirror commented 2026-04-11 01:48:36 -05:00
Author
Owner
Copy Link
Copy Source

@lucasmz-dev commented on GitHub (Jan 31, 2026):

Yep I have the same issue.

I don't see why it would be due to microG or anything, though I am also using it here

I use IronFox, and I'm using GitHub as a test login.This was an issue I noticed when trying the CIs versions a while ago for translation purposes, but ignored it and didn't even report due to not being an actual version and being a big enough issue to be noticeable...

As described, returning to 2025.12.0 solves the issue

<!-- gh-comment-id:3829237183 --> @lucasmz-dev commented on GitHub (Jan 31, 2026): Yep I have the same issue. I don't see why it would be due to microG or anything, though I am also using it here I use IronFox, and I'm using GitHub as a test login.This was an issue I noticed when trying the CIs versions a while ago for translation purposes, but ignored it and didn't even report due to not being an actual version and being a big enough issue to be noticeable... As described, returning to 2025.12.0 solves the issue
GiteaMirror commented 2026-04-11 01:48:37 -05:00
Author
Owner
Copy Link
Copy Source

@lucasmz-dev commented on GitHub (Jan 31, 2026):

What seems weird to me is how this is seemingly only broken in custom ROMs, and only after a version

What even changed?

I wouldn't blame microG because like, it works without it AFAIK, and it also shouldn't even be an involved party when using IronFox and such, it just uses the usual android APIs...

In fact I had a much better experience with degoogled ROMs with Bitwarden than googled ROMs in the past, where apps would be forced to use GMS when I didn't want them to

<!-- gh-comment-id:3829256657 --> @lucasmz-dev commented on GitHub (Jan 31, 2026): What seems weird to me is how this is seemingly only broken in custom ROMs, and only after a version What even changed? I wouldn't blame microG because like, it works without it AFAIK, and it also shouldn't even be an involved party when using IronFox and such, it just uses the usual android APIs... In fact I had a much better experience with degoogled ROMs with Bitwarden than googled ROMs in the past, where apps would be forced to use GMS when I didn't want them to
GiteaMirror commented 2026-04-11 01:48:37 -05:00
Author
Owner
Copy Link
Copy Source

@lucasmz-dev commented on GitHub (Jan 31, 2026):

For reference, I'm using a bangkk (moto g84) on LineageOS with avbroot (unrooted mode) so relocked.

<!-- gh-comment-id:3829269496 --> @lucasmz-dev commented on GitHub (Jan 31, 2026): For reference, I'm using a bangkk (moto g84) on LineageOS with avbroot (unrooted mode) so relocked.
GiteaMirror commented 2026-04-11 01:48:38 -05:00
Author
Owner
Copy Link
Copy Source

@lucasmz-dev commented on GitHub (Jan 31, 2026):

I wouldn't be surprised if this is some sort of bug caused by a difference in actual AOSP/"stock" software

Similar to how Google broke app link verification in AOSP

<!-- gh-comment-id:3829272700 --> @lucasmz-dev commented on GitHub (Jan 31, 2026): I wouldn't be surprised if this is some sort of bug caused by a difference in actual AOSP/"stock" software Similar to how Google broke app link verification in AOSP
GiteaMirror commented 2026-04-11 01:48:38 -05:00
Author
Owner
Copy Link
Copy Source

@lucasmz-dev commented on GitHub (Jan 31, 2026):

Here are my logs as well:

bitwarden_flight_recorder254373985400375352.zip

There should be 2 or 3 attempts at login in these.

<!-- gh-comment-id:3829283759 --> @lucasmz-dev commented on GitHub (Jan 31, 2026): Here are my logs as well: [bitwarden_flight_recorder254373985400375352.zip](https://github.com/user-attachments/files/24985802/bitwarden_flight_recorder254373985400375352.zip) There should be 2 or 3 attempts at login in these.
GiteaMirror commented 2026-04-11 01:48:39 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Feb 1, 2026):

Hi @rmcdowell-bitwarden the issue is not related to Vaultwarden or any server but seems like an issue with the Bitwarden app used on Custom ROMs. Can you consider opening the issue again?

<!-- gh-comment-id:3830314174 --> @wheremygit commented on GitHub (Feb 1, 2026): Hi @rmcdowell-bitwarden the issue is not related to Vaultwarden or any server but seems like an issue with the Bitwarden app used on Custom ROMs. Can you consider opening the issue again?
GiteaMirror commented 2026-04-11 01:48:40 -05:00
Author
Owner
Copy Link
Copy Source

@UjuiUjuMandan commented on GitHub (Feb 1, 2026):

Here are my logs as well:

bitwarden_flight_recorder254373985400375352.zip

There should be 2 or 3 attempts at login in these.

Unfortunately I can't see anything useful logged in this or mine or wheremygit's.

<!-- gh-comment-id:3830386670 --> @UjuiUjuMandan commented on GitHub (Feb 1, 2026): > Here are my logs as well: > > [bitwarden_flight_recorder254373985400375352.zip](https://github.com/user-attachments/files/24985802/bitwarden_flight_recorder254373985400375352.zip) > > There should be 2 or 3 attempts at login in these. Unfortunately I can't see anything useful logged in this or mine or wheremygit's.
GiteaMirror commented 2026-04-11 01:48:40 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Feb 1, 2026):

@lucasmz-dev:

What seems weird to me is how this is seemingly only broken in custom ROMs

And additionally not in all custom ROMs. -- I installed LineageOS on the Motorola G9 Play devices of my parents a while ago. And I just successfully created a passkey, stored in the BW vault, and can log in with it. No error message.

(BW mobile app 2026.1.0, Android 16 / LineageOS 23.0 with Google Apps/Services, tested on Brave)

<!-- gh-comment-id:3831269896 --> @pamperer562580892423 commented on GitHub (Feb 1, 2026): @lucasmz-dev: > What seems weird to me is how this is seemingly only broken in custom ROMs And additionally not in all custom ROMs. -- I installed LineageOS on the Motorola G9 Play devices of my parents a while ago. And I just successfully created a passkey, stored in the BW vault, and can log in with it. No error message. (BW mobile app 2026.1.0, Android 16 / LineageOS 23.0 with Google Apps/Services, tested on Brave)
GiteaMirror commented 2026-04-11 01:48:41 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Feb 1, 2026):

@pamperer562580892423 so then Custom ROMs based on Android 15?

<!-- gh-comment-id:3831390420 --> @wheremygit commented on GitHub (Feb 1, 2026): @pamperer562580892423 so then Custom ROMs based on Android 15?
GiteaMirror commented 2026-04-11 01:48:41 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Feb 1, 2026):

@pamperer562580892423 so then Custom ROMs based on Android 15?

Maybe. Or still maybe something else.

Just to rule out the browser: did you try it with Chrome or Brave - and their "autofill integrations" enabled? (see e.g. here: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941#p-199071-h-33-for-chrome-and-brave-use-the-new-autofill-integration-you-can-skip-that-if-you-dont-use-chrome-or-brave-9)

<!-- gh-comment-id:3831420981 --> @pamperer562580892423 commented on GitHub (Feb 1, 2026): > [@pamperer562580892423](https://github.com/pamperer562580892423) so then Custom ROMs based on Android 15? Maybe. Or still maybe something else. Just to rule out the browser: did you try it with Chrome or Brave - and their "autofill integrations" enabled? (see e.g. here: https://community.bitwarden.com/t/short-guide-tips-autofill-on-android/88941#p-199071-h-33-for-chrome-and-brave-use-the-new-autofill-integration-you-can-skip-that-if-you-dont-use-chrome-or-brave-9)
GiteaMirror commented 2026-04-11 01:48:42 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Feb 1, 2026):

Ok I got interesting results. So I didn't want to reinstall BW again, I decided to create a work profile with Shelter and install the newer version of BW there with their server and a test account. I first tried with Cromite and it returned the same error. Then I installed brave and tried there, the app just froze. Tried it multiple times same result. I wanted to take a screenshot of it so I enabled "allow screen capture" in BW and tried in Brave again and this time it worked — I was able to create a passkey and login with it. Then I tried with Firefox and it worked there as well. So did Google Chrome (Interesting observation with Chrome was that instead of BW's logo on the autofill screen, it showed Google Password Manager's Logo even though it showed passkeys from BW). Then I tried Fennec and it returned the same original error as Cromite.

I had "autofill integrations" and "Android Credential" Integration in all the chromium browsers enabled by default. Firefox browsers didn't seem to have those options but Vanilla Firefox worked with 2026.1.0.

tried 2026.1.0 on my mom’s pixel 9 with Stock Android 16. It works fine over there.

I tested this on Brave as well.

@pamperer562580892423 Would you be able to check on Cromite and Fennec on your device to rule out device and Android Version or ROM specific behavior?

<!-- gh-comment-id:3831746087 --> @wheremygit commented on GitHub (Feb 1, 2026): Ok I got interesting results. So I didn't want to reinstall BW again, I decided to create a work profile with Shelter and install the newer version of BW there with their server and a test account. I first tried with Cromite and it returned the same error. Then I installed brave and tried there, the app just froze. Tried it multiple times same result. I wanted to take a screenshot of it so I enabled "allow screen capture" in BW and tried in Brave again and this time it worked — I was able to create a passkey and login with it. Then I tried with Firefox and it worked there as well. So did Google Chrome (Interesting observation with Chrome was that instead of BW's logo on the autofill screen, it showed Google Password Manager's Logo even though it showed passkeys from BW). Then I tried Fennec and it returned the same original error as Cromite. I had "autofill integrations" and "Android Credential" Integration in all the chromium browsers enabled by default. Firefox browsers didn't seem to have those options but Vanilla Firefox worked with 2026.1.0. > tried 2026.1.0 on my mom’s pixel 9 with Stock Android 16. It works fine over there. I tested this on Brave as well. @pamperer562580892423 Would you be able to check on Cromite and Fennec on your device to rule out device and Android Version or ROM specific behavior?
GiteaMirror commented 2026-04-11 01:48:43 -05:00
Author
Owner
Copy Link
Copy Source

@refactoriel commented on GitHub (Feb 1, 2026):

Same problem on my phone
GrapheneOS Android 16 2026012801
Bitwarden Version 2026.1.0
Ironfox 147.0.2
Vanadium (i.e. Chrome) Version 144.0.7559.109.0

Vanadium works fine, Ironfox doesn't. It used to work fine, too.

<!-- gh-comment-id:3831772659 --> @refactoriel commented on GitHub (Feb 1, 2026): Same problem on my phone GrapheneOS Android 16 2026012801 Bitwarden Version 2026.1.0 Ironfox 147.0.2 Vanadium (i.e. Chrome) Version 144.0.7559.109.0 Vanadium works fine, Ironfox doesn't. It used to work fine, too.
GiteaMirror commented 2026-04-11 01:48:43 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Feb 1, 2026):

@wheremygit As @refactoriel now wrote, Ironfox wouldn't work, and I already have Ironfox on my phone, I just tested this.

And I can say, with Ironfox, I now also saw that "App not supported" error message from the BW app 2026.1.0.

Furthermore, I got those error messages:

Image Image

 

As you can see, I tried to log in with passkey on the BW community forum. [PS: as I already got those errors for login/authentication, I didn't see the need to try passkey creation on Ironfox...]

My phone (don't know, if I posted it here already):

© Bitwarden Inc. 2015-2026

Version: 2026.1.0 (21141)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc
💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1
🦀 SDK: 2.0.0-4441-c5a3b833
🌩 Server: 2026.1.0 @ EU

<!-- gh-comment-id:3831798223 --> @pamperer562580892423 commented on GitHub (Feb 1, 2026): @wheremygit As @refactoriel now wrote, Ironfox wouldn't work, and I already have Ironfox on my phone, I just tested this. And I can say, with Ironfox, I now also saw that "App not supported" error message from the BW app 2026.1.0. Furthermore, I got those error messages: <img width="500" height="1103" alt="Image" src="https://github.com/user-attachments/assets/027728aa-badf-4879-8973-3c184ca65459" /> <img width="500" height="1103" alt="Image" src="https://github.com/user-attachments/assets/a7dd4797-6fdb-4b48-9e84-9b8172bdaf4f" /> &nbsp; As you can see, I tried to log in with passkey on the BW community forum. [PS: as I already got those errors for login/authentication, I didn't see the need to try passkey creation on Ironfox...] My phone (don't know, if I posted it here already): © Bitwarden Inc. 2015-2026 Version: 2026.1.0 (21141) 📱 Fairphone FP5 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2026.1-rc42@67f83e3020b53f8d41e63a7d8f6bdb759ccb9ddc 💻 build source: bitwarden/android/actions/runs/21299199924/attempts/1 🦀 SDK: 2.0.0-4441-c5a3b833 🌩 Server: 2026.1.0 @ EU
GiteaMirror commented 2026-04-11 01:48:44 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Feb 1, 2026):

@wheremygit Do you still need tests with Cromite or Fennec? -- This already now looks like a browser issue, or rather probably a regression of the BW mobile app in compatibility with some browsers.

But maybe a few more tests should be done, to be certain about that...

PS: @UjuiUjuMandan You also mentioned Cromite and Fennec... so, @UjuiUjuMandan and @lucasmz-dev you could also try if Chrome, Brave or Vanadium (I think Firefox was reported here with mixed results) work on your devices or not.

<!-- gh-comment-id:3831824083 --> @pamperer562580892423 commented on GitHub (Feb 1, 2026): @wheremygit Do you still need tests with Cromite or Fennec? -- This already now looks like a browser issue, or rather probably a regression of the BW mobile app in compatibility with some browsers. But maybe a few more tests should be done, to be certain about that... PS: @UjuiUjuMandan You also mentioned Cromite and Fennec... so, @UjuiUjuMandan and @lucasmz-dev you could also try if Chrome, Brave or Vanadium (I think Firefox was reported here with mixed results) work on your devices or not.
GiteaMirror commented 2026-04-11 01:48:45 -05:00
Author
Owner
Copy Link
Copy Source

@pamperer562580892423 commented on GitHub (Feb 2, 2026):

Maybe also check whether those other browsers like Cromite, Fennec... are on the list of the "privileged apps" (BW Android app --> Settings --> Autofill --> Privileged apps // belongs to the "Passkey management" section). -- In my case, Ironfox is. And I would guess, every app, that is listed there, is expected to work, so it would be a bug if they didn't work.

<!-- gh-comment-id:3832371011 --> @pamperer562580892423 commented on GitHub (Feb 2, 2026): Maybe also check whether those other browsers like Cromite, Fennec... are on the list of the "privileged apps" (BW Android app --> Settings --> Autofill --> Privileged apps // belongs to the "Passkey management" section). -- In my case, Ironfox is. And I would guess, every app, that is listed there, is expected to work, so it would be a bug if they didn't work.
GiteaMirror commented 2026-04-11 01:48:45 -05:00
Author
Owner
Copy Link
Copy Source

@wheremygit commented on GitHub (Feb 2, 2026):

browsers like Cromite, Fennec... are on the list of the "privileged apps"

Yes they are in privileged list by default.

probably a regression of the BW mobile app

Seems like it now. Will have to wait for an update from BW or the browsers to see if it fixes it.

<!-- gh-comment-id:3833032516 --> @wheremygit commented on GitHub (Feb 2, 2026): > browsers like Cromite, Fennec... are on the list of the "privileged apps" Yes they are in privileged list by default. > probably a regression of the BW mobile app Seems like it now. Will have to wait for an update from BW or the browsers to see if it fixes it.
GiteaMirror commented 2026-04-11 01:48:46 -05:00
Author
Owner
Copy Link
Copy Source

@UjuiUjuMandan commented on GitHub (Feb 11, 2026):

So, I believe https://github.com/bitwarden/android/pull/6502 will fix this, it's an additional , breaking the privileged app list in JSON.

<!-- gh-comment-id:3881944010 --> @UjuiUjuMandan commented on GitHub (Feb 11, 2026): So, I believe https://github.com/bitwarden/android/pull/6502 will fix this, it's an additional `,` breaking the privileged app list in JSON.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#8475