For the deep linking setup, the following information must be entered into the Airbridge dashboard.

• iOS URI scheme: The Airbridge deep link is converted to a scheme deep link using the iOS URI scheme.

• iOS App ID: The universal link domain of the Airbridge deep link is set using the iOS App ID.

• Android URI scheme: The Airbridge deep link is converted to a schema deep link using the Android URI scheme. This information is necessary for the App Link and URI scheme.

• Package name: This is the Android app identifier necessary for the App Link and URI scheme.

• Android sha256_cert_fingerprints: This is used for setting the App Link domain. This information is necessary for the App Link.

Attention

To properly redirect users as intended, submit different information for the production app and the development app.

Follow the steps below to enter the above information into the Airbridge dashboard.

1. Go to [Tracking Link]>[Deep Links] in the Airbridge dashboard.

2. Enter the iOS URI scheme in the iOS URI Scheme field. Include ://. For example, if the iOS URI scheme is demo, you enter it as demo://.

3. In the Apple Developer Dashboard, go to [Identifier] of the app you want to set up the deep link. Find the App ID Prefix and Bundle ID.

4. The iOS App ID is in the format of App ID Prefix+ .+ Bundle ID. Enter the iOS App ID into the iOS App ID field. For example, if the App ID Prefix is prefix and the Bundle ID is example, the iOS App ID is prefix.example.

1. Go to [Tracking Link]>[Deep Links] in the Airbridge dashboard.

2. Enter the Android URI scheme into the Android URI Scheme field. Include ://. For example, if the URI scheme is demo, you must enter it as demo://.

3. Enter the package name in the Package name field.

4. You need to find the sha256_cert_fingerprints. Run the following command from the keystore file you are deploying.

keytool -list -v -keystore YOUR_KEYSTORE.keystore

Find the SHA256 value in the results. The SHA256 value is the sha256_cert_fingerprints.

Certificate fingerprints:
    MD5:  4C:65:04:52:F0:3F:F8:65:08:D3:71:86:FC:EF:C3:49
    SHA1: C8:BF:B7:B8:94:EA:5D:9D:38:59:FE:99:63:ED:47:B2:D9:5A:4E:CC
    SHA256: B5:EF:4D:F9:DC:95:E6:9B:F3:9A:5E:E9:D6:E0:D8:F6:7B:AB:79:C8:78:67:34:D9:A7:01:AB:6A:86:01:0E:99

5. Enter the SHA256 value into the sha256_cert_fingerprints field.

Configure the app to launch with an Airbridge deep link when the user clicks on a tracking link.

1. To set up the scheme deep link to your app, go to [YOUR_PROJECT]>[Info]>[URL Types] in Xcode.

2. Click + and enter the iOS URI scheme you submitted in the Airbridge dashboard in the URL Schemes field.

Attention

When entering the iOS URL scheme, exclude ://.

3. To set up the universal link to your app, go to [YOUR_PROJECT]>[Signing & Capabilities] in Xcode.

4. Click + Capability to add Associated Domains.

5. Add applinks:YOUR_APP_NAME.airbridge.io and applinks:YOUR_APP_NAME.abr.ge to Associated Domains.

YOUR_APP_NAME is the Airbridge app name.

Attention

If you are using or plan to use the Password AutoFill feature, you must add the Webcredentials domain. A situation may arise where the domain of the password saved through the Password AutoFill feature appears as airbridge.io or abr.ge to your app users.

Refer to thisarticle for more details.

1. To set up the scheme deep link to your app, add an intent filter to the Activity that handles deep links in the AndroidManifest.xml.

The intent filter you add must use the Android URI Scheme you entered into the Airbridge dashboard.

<activity ...>
    ...
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />

        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />

        <data android:scheme="YOUR_SCHEME" />
    </intent-filter>
    ...
</activity>

Attention

When entering the Android URI Scheme, exclude ://.

2. To set up the App Links to your app, add an intent filter under the Activity that handles the deep link in the AndroidManifest.xml.

YOUR_APP_NAME is the Airbridge app name.

<activity ...>
    ...
    <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="http" android:host="YOUR_APP_NAME.abr.ge" />
        <data android:scheme="https" android:host="YOUR_APP_NAME.abr.ge" />
    </intent-filter>
    <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="http" android:host="YOUR_APP_NAME.airbridge.io" />
        <data android:scheme="https" android:host="YOUR_APP_NAME.airbridge.io" />
    </intent-filter>
    ...
</activity>

Pass deep link events to the Airbridge SDK for collection. Call the Airbridge.trackDeeplink function at the top of the OS callback that is called when the app is opened with a deep link.

Please add the following code to the ios/YOUR_PROJECT_NAME/AppDelegate.m file.

#import <airbridge_flutter_sdk/AirbridgeFlutter.h>
...
// when app is opened with scheme deeplink
- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
    // track deeplink
    [AirbridgeFlutter trackDeeplinkWithUrl:url];

    return YES;
}
...
// when app is opened with universal links
- (BOOL)application:(UIApplication *)application continueUserActivity:(NSUserActivity *)userActivity restorationHandler:(void (^)(NSArray<id<UIUserActivityRestoring>> * _Nullable))restorationHandler {
    // track deeplink
    [AirbridgeFlutter trackDeeplinkWithUserActivity:userActivity];

    return YES;
}

import airbridge_flutter_sdk
...
// when app is opened with scheme deeplink
func application(
    _ app: UIApplication,
    open url: URL,
    options: [UIApplication.OpenURLOptionsKey : Any] = [:]
) -> Bool {
    // track deeplink
    AirbridgeFlutter.trackDeeplink(url: url)

    return true
}
...
// when app is opened with universal links
func application(
    _ application: UIApplication,
    continue userActivity: NSUserActivity,
    restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void
) -> Bool {
    // track deeplink
    AirbridgeFlutter.trackDeeplink(userActivity: userActivity)

    return true
}

Please add the following code to the android/app/src/main/java/.../MainApplication.kt file.

import co.ab180.airbridge.flutter.AirbridgeFlutter
...
override fun onResume() {
    super.onResume()
    AirbridgeFlutter.trackDeeplink(intent)
}
...
override fun onNewIntent(intent: Intent?) {
    super.onNewIntent(intent)
    setIntent(intent)
}

import co.ab180.airbridge.flutter.AirbridgeFlutter;
...
@Override
protected void onResume() {
    super.onResume();
    AirbridgeFlutter.trackDeeplink(intent);
}
...
@Override
public void onNewIntent(Intent intent) {
    super.onNewIntent(intent);
    setIntent(intent);
}

When the Airbridge deeplink is executed, it is converted into a scheme deeplink and passed on to the OnDeeplinkReceived callback. And if a deeplink that is not an Airbridge deeplink is executed, it is delivered to the callback without conversion.

Utilize the received deeplink to send the user to the set destination.

Airbridge.setOnDeeplinkReceived((deeplink) {
    // show proper content using url
});

If you only need to receive the Airbridge Deeplink, you can only receive the Airbridge Deeplink through a callback by setting isHandleAirbridgeDeeplinkOnly to true in Configure SDK. For more information, please refer to the section on receiving only the Airbridge Deeplink

The Airbridge SDK attempts to retrieve a deep link after initializing the SDK when all the following conditions are met. If the app is closed during retrieval, the Airbridge SDK treats it as if there is no stored Airbridge deep link.

• The Airbridge.startTracking function is called with the opt-in settings in place. Or, opt-in has not been set.

• The ATT tracking response has been determined. Or, the event collection delay time set in the ATT prompt has expired.