docs(passkeys): document Android Digital Asset Links setup#256
Merged
Conversation
Vinzent03
approved these changes
Jun 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an Android Digital Asset Links (
assetlinks.json) setup entry to thepasskeyspackage README, under the platform notes in the Troubleshooting section.Why
The README documents the relying-party association setup for macOS (Apple App Site Association + Associated Domains) and the web SDK setup for Web, but there is no equivalent for Android. The existing Android section only covers emulator / Google-account troubleshooting, so a developer setting up passkeys on Android has no in-README pointer to hosting
assetlinks.json, which is required for the platform to associate the app with the relying party.This came up while integrating
passkeysintosupabase_flutter, where we want to link users to the plugin's own docs for per-platform setup rather than duplicating it downstream.How
Configure Digital Asset Links (assetlinks.json)entry as the first item in the Android section, mirroring the existing macOS AASA entry (hosting location, the required statement with package name and signing-certificate SHA-256 fingerprints, RPID matching the host domain, no redirects,application/jsoncontent type), with an example file.Docs only, no code changes.