Windows 10 已于2025年10月14日停止支持。如果您正在使用 Windows 10,参见 这篇文章

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解
Solved 已存档

Firefox Passkeys not working - all passkeys generated in firefox android are instant lost.

elbea64 已回复
elbea64

I use Firefox Android and Bitwarden Password Manager.

When I try to generate a passkey for some website Firefox asks me for the device to store the passkey. The only suitable Option is "This Device". When I tap it, i am asked for authentification (Fingerprint). After Authentification the website gives me a success message and the whole process is complete but the passkey isn't stored anywhere.

In every other browser on android I am asked for the entry in Bitwarden where the passkey should be stored. On windows this works with Firefox

Is it intended to work only when passkeys are stored in Firefox itself? At least a hint that it doesn't work with external Password Managers would be helpful - lost passkeys are a pain

I use Firefox Android and Bitwarden Password Manager. When I try to generate a passkey for some website Firefox asks me for the device to store the passkey. The only suitable Option is "This Device". When I tap it, i am asked for authentification (Fingerprint). After Authentification the website gives me a success message and the whole process is complete but the passkey isn't stored anywhere. In every other browser on android I am asked for the entry in Bitwarden where the passkey should be stored. On windows this works with Firefox Is it intended to work only when passkeys are stored in Firefox itself? At least a hint that it doesn't work with external Password Managers would be helpful - lost passkeys are a pain

所有回复 (2)

Oh, I forgot that passkeys stored in Bitwarden can be used to login in Firefox Android if they are generated somewhere else

选择的解决方案

After some further investigation passkey-generation works correctly under Firefox Nightly, so it looks like the problem will be solved within the next releases.

This topic could be closed.