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

Thanks @androidacy-user, we are aware of this and we maintain a community list to allow lesser known but vetted browsers: https://github.com/bitwarden/android/blob/main/app/src/main/assets/fido2_privileged_community.json

Once you make a PR, adding a browser there, it would be included in the next release.

We are however looking into improving this even further, is that something you would be interested in?

If you list them, I can get them added.

then why is a browser in that list not working (quetta)? do you genuinely think it's reasonable for user(s) to have to validate against a list (that is linked nowhere in the app!) before they switch browsers?

or do you think it's pretty reasonable to have my password manager (that I use to make my life easier, not harder) to at least allow me to "trust" a browser, so that my logins "just work", instead? (not even going to mention non whitelisted browsers aren't even detected as browsers, and bitwarden tries to fill logins for the app instead of the website).

idk what the perfect solution is but this is not it

then why is a browser in that list not working (quetta)? do you genuinely think it's reasonable for user(s) to have to validate against a list (that is linked nowhere in the app!) before they switch browsers?

most likely an update with that commit hasn't come out yet
try getting the latest release from github

I'm not sure if all lesser-known Android browsers haven't been recognized by Bitwarden to use passkeys, but it's strange that Firefox Nightly still has problems with Bitwarden

On the other hand, Vivaldi Snapshot (for Android) works very well with Bitwarden when using passkeys.

So, I hope Firefox Nightly will be whitelisted in a future not so far.

@gabeweb Firefox nightly was whitelisted in #5045. It will be in our next release.

As a more general update, we will be introducing the ability to individually manage trusted browsers in an upcoming release (see #4862 and #4898). This means there will no longer be a need to maintain a "community" privileged app list. When a request is received from an untrusted source, users will be given the option to trust it and continue, or reject the request.

@gabeweb Firefox nightly was whitelisted in #5045. It will be in our next release.

As a more general update, we will be introducing the ability to individually manage trusted browsers in an upcoming release (see #4862 and #4898). This means there will no longer be a need to maintain a "community" privileged app list. When a request is received from an untrusted source, users will be given the option to trust it and continue, or reject the request.

Highly appreciated :)

I think that will resolve the issue for both sides. I'm not sure if it's implemented in the current PRs but a checkbox to remember the choice would be even more appreciated!

The linked PR's will remember the privileged app if you chose to trust it. There are also screens in Settings that will allow you to view and remove applications you've previously chosen to trust. The community list we maintain and the Google list will be continue to be read-only.

@gabeweb Firefox nightly was whitelisted in #5045. It will be in our next release.

As a more general update, we will be introducing the ability to individually manage trusted browsers in an upcoming release (see #4862 and #4898). This means there will no longer be a need to maintain a "community" privileged app list. When a request is received from an untrusted source, users will be given the option to trust it and continue, or reject the request.

Thank you for the reply and the good news! 🙌🏻