Repository navigation
chore: add Play app signing key to assetlinks.json - #103
Merged
Merged
Conversation
Google Play re-signs the app with its own key, so App Links only verify for Play installs if this fingerprint is listed. The upload key stays listed for sideloaded release builds. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
6 of 11 tasks
This branch was successfully deployed
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
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.
Summary
Google Play re-signs BookBridge with the Play app signing key, so Android App Links (
bookbridge.devsafe.cm/l/...) will only auto-open the app for Play installs if that key's SHA-256 is listed inassetlinks.json.Closes #
Changes
8F:A5:…:63:01to thecm.devsafe.bookbridgeentry. The existing upload-key fingerprint is kept for sideloaded release builds.Test plan
python3 -m json.tool landingPage/static/.well-known/assetlinks.json: valid JSONAfter deploy:
curl https://bookbridge.devsafe.cm/.well-known/assetlinks.jsonand check with Google's Statement List testerflutter analyzeandflutter testpass (app changes) — N/Acargo fmt,cargo clippy, andcargo testpass (Rust core changes) — N/ANew migrations are idempotent and tested against a local or branch database — N/A
Checklist
dev, notmainScreenshots
N/A