Skip to content

docs(journeys): App Links verify for Play and release builds - #478

Merged
jvsena42 merged 1 commit into
mainfrom
docs/journey-15-app-links-verified
Oct 9, 2026
Merged

jvsena42 merged 1 commit into
mainfrom
docs/journey-15-app-links-verified

Conversation

@jvsena42

@jvsena42 jvsena42 commented Oct 8, 2026

Copy link
Copy Markdown
Owner

Closes #473.

Journey 15 said https://loopky.app links stay unverified until the Play signing fingerprint is added to assetlinks.json. It is already listed:

  • Play Console's app signing key SHA-256 is 09:81:13:2B:…:80:48, the first fingerprint in the file.
  • apksigner verify --print-certs on Loopky-1.5.0.apk from the GitHub release prints the same digest, so the upload key and the Play signing key are the same key.

No change to assetlinks.json was needed. The journey header now says which builds verify, and journeys/README.md lists the one check nobody has run: an unpinned link on a Play install, with adb shell pm get-app-links reading verified. The site README is corrected in jvsena42/loopky.github.io#24.

Docs only; nothing was built or driven.

🤖 Generated with Claude Code

Journey 15 said the https link stays unverified until the Play signing
fingerprint is added to assetlinks.json. It is already listed: Play Console
shows the same SHA-256 as the upload key that signs the release APK. What
does not verify is a debug build whose key is not in the file.

Refs #473

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jvsena42
jvsena42 merged commit 033ebe2 into main Oct 9, 2026
11 checks passed
@jvsena42
jvsena42 deleted the docs/journey-15-app-links-verified branch October 9, 2026 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

assetlinks.json may be missing the Play App Signing fingerprint

1 participant