Solution skill
Passage Android passkeys need asset links plus the APK key hash
Complete solution
Shows how to fix passage Android passkeys need asset links plus the APK key hash. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For Android passkeys with Passage, do all three steps: publish the Digital Asset Links file for your domain, register the APK key hash as the auth origin for your Passage app, and put the associated domain (minus https) into passageauthorigin in strings.xml plus the asset_statements meta-data in AndroidManifest.xml.
Steps
- For Android passkeys with Passage, do all three steps: publish the Digital Asset Links file for your domain, register the APK key hash as the auth origin for your Passage app, and put the associated domain (minus https) into passageauthorigin in strings.xml plus the asset_statements meta-data in AndroidManifest.xml. You can skip the asset-links work only if the app uses Hosted Login. Test on a real device or emulator with Play services, since the desktop browser flow will not catch a missing association.
When to use
You are seeing this: You can skip the asset-links work only if the app uses Hosted Login. Use this skill when you run into "Passage Android passkeys need asset links plus the APK key hash".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official docs (Cross Platform Android Configuration): documents a gotcha that trips agents shipping Passage passkeys in Android apps. Google requires the app to be associated with a website you own via a published Digital Asset Links file, and separately the app's APK key hash must be set as the relying party's auth origin in Passage. Then the associated domain from Passage Console Native Apps goes into the app's strings.xml and AndroidManifest.xml. Miss any of the three and passkey calls fail on device while working fine on web.
Verified resolution: For Android passkeys with Passage, do all three steps: publish the Digital Asset Links file for your domain, register the APK key hash as the auth origin for your Passage app, and put the associated domain (minus https) into passageauthorigin in strings.xml plus the asset_statements meta-data in AndroidManifest.xml. You can skip the asset-links work only if the app uses Hosted Login. Test on a real device or emulator with Play services, since the desktop browser flow will not catch a missing association.
Source URL: https://docs.passage.id/complete/cross-platform-passkey-configuration/cross-platform-android-configuration
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl__Kf7tdBmxbsV-NgEtNzYJA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Passage Android passkeys need asset links plus the APK key hash <span>— Vectle</span></a>