iP16, IOS18, Yubikey 5C NFC, Passkey Sign-in?
- Dominant language
- Swift
- Stars
- 684
- Forks
- 154
- Avg merge
- 7d 2h
- Merged PRs (30d)
- 32
Description
### Steps To Reproduce
1. Open **YubiKey Manager** go to tab **Interfaces** verify that all boxes under **NFC** are **checked**.
2. Go to **[vault.bitwarden.com -> Settings](https://vault.bitwarden.com/#/settings/security/two-factor)** on a computer and under Providers select **Passkey** add two **YubiKey 5C NFC**, make sure to save on **Security Key** and not fail like i did at first and save it in Windows..
3. On iPhone try to sign-in using **WebAuthn**. "Error has occurred".
Might just be that I'm not understanding every part of this or missing something but i have been emailing back and forth with Ethan at support and i think hes getting frustrated with me!
### Expected Result
Successful sign-in.
### Actual Result
Error has occurred.
### Screenshots or Videos
_No response_
### Additional Context
_No response_
### Build Version
2024.9.2
### Environment Details
iPhone 16 Pro Max. IOS 18.
YubiKey 5C NFC. Firmware 5.2.7
Bitwarden iPhone app 2024.9.2
Yubikey Manager 1.2.6
Yubico Authenticator 7.0
### 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.
Contributor guide
Research direction
Start by reproducing the WebAuthn sign-in flow in the Bitwarden iPhone app 2024.9.2 using an iPhone 16 Pro Max on iOS 18 and a YubiKey 5C NFC. Compare the passkey provider setup and the reported error, then identify whether successful sign-in can be restored or the limitation documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100