macOS passkey support is broken in macOS 13.6.5
Categories
(Core :: DOM: Web Authentication, defect, P1)
Tracking
()
People
(Reporter: jschanck, Assigned: jschanck)
References
Details
In macOS 13.6.5 (but not earlier) passkey creation and assertion fail silently. The platform prompt is not visible and promises are not rejected.
This was first reported in Bug 1884574, where the issue was causing a diagnostic assertion crash. The issue seems similar to Bug 1865128.
Assignee | ||
Comment 1•1 year ago
|
||
Also, autofill credentials from iCloud keychain are displayed, but they cannot be used.
Comment 2•1 year ago
|
||
:jshanck Should this be an S2? do you think you can find a regressor?
Assignee | ||
Comment 3•1 year ago
|
||
Yes, S1 is too high. Since I opened this, I've learned that this is a bug in macOS. There's probably nothing we can do here. We're expecting a fix from Apple soon.
Assignee | ||
Updated•1 year ago
|
Tested in Firefox 124.0.1 (64-bit), macOS 13.6.6 and things seem to work as expected. Was able to register and authenticate on https://webauthn.io/ as exected with iCloud Keychain enabled.
Comment 7•1 year ago
|
||
I am also no longer able to reproduce this issue with 13.6.6 and hardware security keys.
I just updated Safari to 17.4.1 without rebooting or relaunching Firefox, and passkey is working now. I am still at macOS 13.6.5.
MacOS 13.6.6 with Firefox 124.0.2 is broken as well, yubikey authentication fails silently
testing on https://www.yubico.com/genuine/
Comment 10•1 year ago
|
||
I just updated Safari to 17.4.1 without rebooting or relaunching Firefox, and passkey is working now.
It's strange that safari is somehow a dependency for fix for a firefox issue..
Assignee | ||
Comment 11•1 year ago
|
||
Marking this as WONTFIX as there doesn't seem to be anything we can do about systems that have Safari 17.4.0 installed. There's some bad interaction between Safari 17.4.0 and macOS that is breaking all other users of the platform passkey API. Users that are still affected by this bug should upgrade macOS / Safari.
@haoxi.tan, was your issue resolved by upgrading to 17.4.1? If not, please file a new bug.
Description
•