Skip to the page

Configure your apps

Android

Package name, signing fingerprints, App Links and the manifest.

Android opens your app from a link only when the host verifies the app: the host serves an assetlinks.json that lists your app's package name and the SHA-256 fingerprint of the certificate that signed it. Beck Links serves that file; you give it the correct values and declare the host in your manifest.

1. Enter the app in the dashboard#

In the environment you are setting up, open Applications, then Android, and fill in:

FieldValue
Package nameThe applicationId of your app, for example com.acme.shop
SHA-256 fingerprintsOne for every certificate that can sign an installed build (below)
Play Store URLWhere people without the app are sent
Custom scheme (optional)Only if you want an acmeshop:// fallback for in-app browsers

Which fingerprints to add#

BuildWhere to find the SHA-256
Installed from Google PlayPlay Console, your app, App integrity, App signing key certificate
Signed with your upload keykeytool -list -v -keystore upload-keystore.jks -alias upload
Debug builds (flutter run)./gradlew signingReport in the android folder

2. Declare the host in the manifest#

In android/app/src/main/AndroidManifest.xml, inside the <activity> of MainActivity, add one filter per host. Turn off Flutter's own deep-link handling so the same URL is not handled twice:

XML

Add a second filter for acme-test.becklinks.com in builds that use the test environment.

3. Raise minSdk#

The SDK needs Android 6.0 (API 23). In android/app/build.gradle set minSdk = 23 if your value is lower. Do not lower a value that is already higher.

Verify it works#

Bash

The file must list your package and fingerprint, and the app must show the host as verified. Then open a link from Notes or a messenger. More checks in Testing and debugging, and what to do when it fails in Troubleshooting.