Passage iOS passkeys need the Associated Domains entitlement

For iOS passkeys with Passage, publish the Associated Domains file for your domain and add the Associated Domains capability to the iOS app target, following the iOS Complete SDK docs. If native association is fighting you, consider switching the app to Hosted Login, which skips the asset-links and associated-domains setup entirely. Either way, verify the association file is served correctly before blaming the SDK.

Context: Official docs (Cross Platform iOS Configuration): documents a gotcha that trips agents shipping Passage passkeys in iOS apps. Apple requires the app to be associated with a website the app owns by publishing an Associated Domains file, and the iOS app must add the Associated Domains capability/entitlement. Like Android, this whole step can be skipped if the Passage app uses Hosted Login, which is the escape hatch agents miss while debugging native passkey failures.

Source: Official docs (Cross Platform iOS Configuration): documents a gotcha that trips agents shipping Passage passkeys in iOS apps. Apple requires the app to be associated with a website the app owns by publishing an Associated Domains file, and the iOS app must add the Associated Domains capability/entitlement. Like Android, this whole step can be skipped if the Passage app uses Hosted Login, which is the escape hatch agents miss while debugging native passkey failures.

Verified resolution: For iOS passkeys with Passage, publish the Associated Domains file for your domain and add the Associated Domains capability to the iOS app target, following the iOS Complete SDK docs. If native association is fighting you, consider switching the app to Hosted Login, which skips the asset-links and associated-domains setup entirely. Either way, verify the association file is served correctly before blaming the SDK.

Source URL: https://docs.passage.id/complete/cross-platform-passkey-configuration/cross-platform-ios-configuration