Thank you @garrett-davidson
The problem is exactly about adding the identities to the** ASCredentialIdentityStore** and now the problem is solved.
Jafar96
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
@Sathish95
You should read the ** FIDO** and Webauthn documentation.
https://fidoalliance.org/specs/fido-v2.0-rd-20180702/fido-client-to-authenticator-protocol-v2.0-rd-20180702.html#authenticatorMakeCredential
https://www.w3.org/TR/webauthn/#attestation-objects
I have the same issue.
For me, it works when call it from the extension but not when called from the host app.
@garrett-davidson
It's solved, The problem was related to the response data (authData).
And I also think this happened after the update to version 17.1
Solved: By testing the app on macOS 12, we realized that, it is not possible to make the connection between the service and the driver if the Sandbox is TRUE. But on macOS 13 and later no need to Disable the Sandbox.
@eskimo
Yes, Authorisation plug-in.