01a033bc - Invite landing page and app-link files - #28
Draft
TaprootFreak wants to merge 1 commit into
Draft
Conversation
Serves /invite/{code} against the referral landing API, store badges with
an Android install referrer, and well-known files for Universal Links.
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
1 participant
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.
EN:
Adds the personal invite page at /invite/{code}, store badges, and Universal-Link verification files.
DE:
Ergänzt die persönliche Einladungsseite unter /invite/{code}, Store-Badges und die Verifikationsdateien für Universal Links.
Details
/invite/{code}loadsGET /v1/realunit/referral/landing/{code}. Invite greetings use host and guest names; promo codes show the campaign text from the API. Phones get an open-app button (realunit-wallet://invite/{code}) and store badges. The Play Store URL includes an install referrer./.well-known/apple-app-site-associationandassetlinks.jsonare served as JSON. Android SHA-256 fingerprints are left empty until Play App Signing values are filled in.Visual baselines for the new views are not committed; the screenshot job will need a regenerate after this lands.