- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Version 2024.6.2 does not include the final fix for this issue. We are still completing our internal testing, but we plan to submit another release to the store later this week as soon as it is verified.
from the github issue
Finally! And it seems it’s the 2024.6.2 with the actual fix (2024.6.0 seems to have promised a fix that didn’t cover all cases),
Glad to hear this is being worked on, thanks for sharing this. I assumed it was related to my config and was putting off looking into it further.
Is passkeys up and running yet?
I’ve been using them on both my phone and desktop, works great!
Thanks bud for reply. Im now excited to try. 👍
Where on this page can I read about this fix? This link just takes me to the add-on’s general install page.
On that page, you can choose “version history” to get their list of changes, unfortunately for this one all they put was “bug fixes”…
Good news though, this is an open source project, so easy enough to just go to the source…
Github issue: https://github.com/bitwarden/clients/issues/8873
And here’s all of the commits that have gone into it since 2024.5.1: https://github.com/bitwarden/clients/compare/web-v2024.5.1…desktop-v2024.6.2
Thank you so much. I have a hard time navigating that page. I kept finding the Bitwarden site instead of their github.
This actually explains some problems I’ve been having, and I’m thankful there’s a fix. I actually disabled 2fa for a while because I was sick of having to retrieve a code each time I was forced to log back in.
My god finally the pain of getting the “me too on macos snow leopard” emails from the issue tracker is over
