iOS passkey list ignores auto-fill match detection setting #1849

Closed
opened 2025-11-26 22:59:42 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @Janhouse on GitHub (Apr 15, 2024).

Steps To Reproduce

  1. Add passkeys for multiple subdomains.
  2. Set auto fill match rule to "Host".
  3. Use the iOS passkey with Bitwarden

Expected Result

It should respect passkey auto fill match setting.

Actual Result

Observe both passkeys displayed in the list for all subdomains, ignoring the auto fill match setting.

Operating System

iOS

Build Version

7142

Beta

  • Using a pre-release version of the application.
Originally created by @Janhouse on GitHub (Apr 15, 2024). ### Steps To Reproduce 1. Add passkeys for multiple subdomains. 2. Set auto fill match rule to "Host". 3. Use the iOS passkey with Bitwarden ### Expected Result It should respect passkey auto fill match setting. ### Actual Result Observe both passkeys displayed in the list for all subdomains, ignoring the auto fill match setting. ### Operating System iOS ### Build Version 7142 ### Beta - [X] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:59:42 -06:00
Author
Owner

@micahblut commented on GitHub (Apr 16, 2024):

@Janhouse thanks for testing out the iOS passkey beta! Passkeys do not use the login item URI (and therefor the URI match detection) for autofill. They have their own field, the rpId, that is used for matching.

@micahblut commented on GitHub (Apr 16, 2024): @Janhouse thanks for testing out the iOS passkey beta! Passkeys do not use the login item URI (and therefor the URI match detection) for autofill. They have their own field, the rpId, that is used for matching.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1849