Thanks for clarification
arunThottaSuresh
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Did more testing and the WebAuthN API are working fine in WKWebView and SFSafariViewController for Passkey use cases.
By any chance are u seeing this issue while testing with the Shiny sample app.
If so one thing I noticed was
In SignInViewController
When the view appears, we trigger a modal get request line:32
If the user cancels it then as part of the error observer line:36, we trigger a autofill request so we are ready to autofill
From this point on if we try to click on "Create Account", it just fails because there is a autofill request in progress.
One modification I had to do was do a cancel() on the ASAuthorizationController which triggered the autofill request whenever the user explicitly clicks on "Create Account" in the sample app
Hi, Thanks for the confirmation about the attStmt.
Looks like the flow for RP during Passkey enrollment is,
Check for isUserVerifyingPlatformAuthenticatorAvailable to show the Passkey enroll button
Take the user through an enrollment and then reject the enrollment if it has an attStmt(implying it is a non syncing platform authenticator and thus not a Passkey)?
Understand providing this signal is being discussed at the spec level as u mentioned but meanwhile double checking to make sure there is no better way to figure out Passkeys without taking the user through a enrollment.