Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
passkeyhelp2024
10 months agoNew Contributor
preferImmediatelyAvailableCredentials not working for 1Password
Hello all - We are working to enable passkeys for our users and during login, if a passkey is not available or does not exist for a member, we do not want to show the QR code (fallback method). Apple has suggested we use the request option preferImmediatelyAvailableCredentials when calling performRequests to achieve this.
This works fine if the member is only using iCloud Keychain for their password/passkeys storage but when 1password is used, the fallback modal ("Choose how you'd like to sign in to the app) is presented.
Is there a way programmatically - we can avoid this scenario?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
- 1P_Dave
Moderator
Hello passkeyhelp2024! π
Thanks for reaching out! On the iPhone and iPad, the passkey prompt is generated by iOS itself and 1Password just provides the data for the experience. I've raised this with our development team and they report that the
preferImmediatelyAvailableCredentials
option is not currently available to third-party password managers like 1Password.The team plans to file feedback with Apple to see if the situation can be improved in a future iOS update and I would encourage you to personally report this to Apple as well so that they're aware that you're affected.
Let me know if you have any questions. π
-Dave
ref: dev/core/core#29670
- passkeyhelp2024New Contributor
I see. Thank you Dave for getting back to me. Appreciate the quick response.
- 1P_Dave
Moderator
Thanks again for flagging the issue. Hopefully a future update to iOS improves the situation. π
-Dave
- 1P_Dave
Moderator
I hope that you're doing well! Our development team has received word from our friends at Apple that steps have been taken to begin to address the issue in iOS 18 and later. Can you tell me if you're still seeing the same issue when using iOS 18.2.1?
I look forward to hearing from you.
-Dave