Go-live checklist

After this page, links open your app with no browser in between, the first open after an install lands on the right screen, and your keys are where they belong.

On this page 7
  1. 1. Add every SHA-256 fingerprint
  2. 2. Verify App Links on Android
  3. 3. Test a deferred link from Google Play
  4. 4. Set up iPhone
  5. 5. Put keys and links in the right place
  6. Common errors
  7. Next steps
Time
About 30 minutes, plus a first Google Play review (Google says reviews can take up to 7 days, or longer in exceptional cases)
You need
The quickstart done, and access to Play Console (and Apple Developer for iPhone)
Works on
Android, iPhone

1. Add every SHA-256 fingerprint

Android opens your app directly from a link only if your link domain lists the certificate the installed build was signed with. Add all three in Dashboard → Apps & stores:

Build Certificate Where to find it
Local debug builds Debug key The commands below
Release builds you install yourself Upload key Your keystore, or eas credentials
Anything installed from Google Play Play App Signing key (Google's, not yours) Play Console → Test and release → App integrity
Terminal
# Native Android project (Android Studio's shared debug key)
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android | grep SHA256

# React Native, or Expo after `npx expo prebuild`: the project's own debug key
keytool -list -v -keystore android/app/debug.keystore -storepass android | grep SHA256

# EAS Build: choose Android and your build profile; the keystore's SHA-256 is listed
eas credentials

Paste them in any form: upper or lower case, with or without colons. We store them as uppercase pairs joined by colons and refuse anything that isn't a SHA-256 fingerprint.

You should see: your package name and every fingerprint in the file we host:

Terminal
curl https://hilltop.strait.link/.well-known/assetlinks.json

Add a second intent filter next to the custom scheme one from the quickstart:

AndroidManifest.xml
<intent-filter android:autoVerify="true">
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:scheme="https" android:host="hilltop.strait.link" />
</intent-filter>

Reinstall the app (Android checks at install time), then ask the phone:

Terminal
adb shell pm get-app-links com.yourcompany.yourapp

You should see: hilltop.strait.link: verified. Tapping a link now opens the app with no browser flash. If not, paste your domain into the App Links checker.

A link tapped before the app is installed reaches the app through the Google Play Install Referrer, so it only works for builds installed from Google Play:

  1. Upload a build to internal testing in Play Console and add yourself as a tester.
  2. In Dashboard → Apps & stores → People without the app, choose Always Google Play while the app isn't public. (The default sends people to your website when the Play listing isn't live, to avoid Play's "Item not found" page.)
  3. Uninstall the app, tap your link, install from Play, open the app.

The first upload may be reviewed before testers can install it. Google says reviews can take up to 7 days, or longer in exceptional cases (Play Console Help).

You should see: the first open lands on /product/42, and Analytics shows the tap, the install with match method install_referrer, and the open.

4. Set up iPhone

  1. In Dashboard → Apps & stores, add your Apple Team ID, bundle ID and App Store ID.
  2. In Xcode, add the Associated Domains capability with applinks:hilltop.strait.link, and your custom scheme under URL Types.
  3. Read How iPhone install matching works before you fill in the App Store privacy label.
Terminal
curl https://hilltop.strait.link/.well-known/apple-app-site-association

You should see: <Team ID>.<bundle ID> in that file. iOS fetches it through Apple's CDN, which can lag behind changes.

  • Secret key: on your server only, in an environment variable. Create links from your backend with the Node SDK or the REST API, never from the app. See Keys.
  • Link pages: add your app name, icon and colour in Settings → How your link pages look, so the pages people see lead with your brand (App Links).
  • No website? A link's destination can be any https:// URL on a domain you control, such as https://yourapp.com/product/42. Only the path and query reach your app. Desktop visitors go to the full URL, and so do people without the app if you chose "always your website", so make sure that page exists.
  • SMS in India: whitelist your link domain, <handle>.strait.link, in your DLT template like any other URL.

You should see: no secret key anywhere in your app's source or build output (grep -r st_live_ . from the app folder finds nothing).

Common errors

  • Works on a debug build, opens the browser from Play. The Play App Signing fingerprint is missing (step 1).
  • The deferred link opens the home screen. The build was sideloaded, or the app was opened before you tapped the link. The check runs once per install: uninstall and try again.
  • assetlinks.json returns 404. The package name or fingerprints in Apps & stores are empty. More in Troubleshooting.

Next steps