App Credentials
What the dashboard needs to register an app, and where to find each value — bundle IDs, Apple Team ID, App Store ID, package names and signing fingerprints.
When you register an app in the dashboard, you'll need these values.
| Platform | Field | Where to find it |
|---|---|---|
| iOS | Bundle ID | Xcode → General → Identity, or App Store Connect → App Information |
| iOS | Apple Team ID | developer.apple.com → Account → Membership (10-char code) |
| iOS | App Store ID | App Store Connect → App Information → Apple ID (e.g. id1490012345) |
| Android | Package name | Play Console → App signing, or applicationId in app/build.gradle |
| Android | SHA-256 fingerprints | Play Console → Test and release → App integrity → App signing — copy the SHA-256 for both the App signing key and the Upload key. Debug key: keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android |
Register every Android fingerprint you install from — Play-installed builds are signed by Google's app-signing key, sideloads by your upload key, and dev builds by each machine's debug key. A missing fingerprint is the #1 reason App Links open the browser.
Once the domain is live, confirm the files are being served correctly with our free Universal Links & App Links validator — it lists the bundle IDs and fingerprints each file actually declares, so you can check them against what you entered above. No signup.