To see an example application that has the Privy Expo SDK configured with passkeys, check out our Expo starter repo!
If you have not already configured a custom build configuration, follow the custom build configuration guide.
Passkeys require that you associate a website with your app. To do so, you need to have the associated domain file on your website and the appropriate entitlement in your app.
JSON
file with at least the following contentMake sure to use your teamID
and bundleID
in the file hosted on your website.
For more information about supporting associated domains see Apple’s documentation.
Next, update your app.json
(or app.config.ts
) to include the associatedDomains
and deploymentTarget
like so:
Lastly, build your app!
Passkeys require that you associate a website with your app. To do so, you need to have the associated domain file on your website and the appropriate entitlement in your app.
JSON
file with at least the following contentMake sure to use your teamID
and bundleID
in the file hosted on your website.
For more information about supporting associated domains see Apple’s documentation.
Next, update your app.json
(or app.config.ts
) to include the associatedDomains
and deploymentTarget
like so:
Lastly, build your app!
To enable passkey support for your Android app, associate your app with a website that your app owns.
JSON
file with at least the following contentMake sure to use your package_name
and sha256_cert_fingerprint
in the file hosted on your website.
For more information on obtaining the sha256_cert_fingerprint
for your app, see the signing report documentation. For more information about generally supporting Digital Asset Links see Google’s documentation.
You will also need to add your sha256_cert_fingerprint
to the allowed Android key hashes list in the Settings
tab of the Privy dashboard.
Next, update your app.json
(or app.config.ts
) to look like:
Lastly, build your app!
To see an example application that has the Privy Expo SDK configured with passkeys, check out our Expo starter repo!
If you have not already configured a custom build configuration, follow the custom build configuration guide.
Passkeys require that you associate a website with your app. To do so, you need to have the associated domain file on your website and the appropriate entitlement in your app.
JSON
file with at least the following contentMake sure to use your teamID
and bundleID
in the file hosted on your website.
For more information about supporting associated domains see Apple’s documentation.
Next, update your app.json
(or app.config.ts
) to include the associatedDomains
and deploymentTarget
like so:
Lastly, build your app!
Passkeys require that you associate a website with your app. To do so, you need to have the associated domain file on your website and the appropriate entitlement in your app.
JSON
file with at least the following contentMake sure to use your teamID
and bundleID
in the file hosted on your website.
For more information about supporting associated domains see Apple’s documentation.
Next, update your app.json
(or app.config.ts
) to include the associatedDomains
and deploymentTarget
like so:
Lastly, build your app!
To enable passkey support for your Android app, associate your app with a website that your app owns.
JSON
file with at least the following contentMake sure to use your package_name
and sha256_cert_fingerprint
in the file hosted on your website.
For more information on obtaining the sha256_cert_fingerprint
for your app, see the signing report documentation. For more information about generally supporting Digital Asset Links see Google’s documentation.
You will also need to add your sha256_cert_fingerprint
to the allowed Android key hashes list in the Settings
tab of the Privy dashboard.
Next, update your app.json
(or app.config.ts
) to look like:
Lastly, build your app!