Troubleshooting - Unreal SDK - Airbridge Help Center

iOS

[Xcode 27] SceneDelegate Migration Required — Additional Setup Needed for Airbridge Deep Links

AttentionThis troubleshooting guide is for customers who need to migrate an existing AppDelegate-based app to UIScene(SceneDelegate) lifecycle.

Symptoms

When an app built with Xcode 27 is launched, the app may not run properly.
Airbridge deep link events are not collected even when the app is opened through a scheme deep link or Universal Link.
The app does not work even though the code was added to AppDelegate as shown in the Initialize SDK and Collect deep link events in your app developer guide examples.

Cause

Apple is moving the app lifecycle from the UIApplicationDelegate-only AppDelegate model to the UIScene-based SceneDelegate model, and adopting the Scene lifecycle has effectively become required in the latest Xcode and iOS environments.When an app adopts the Scene lifecycle through UIApplicationSceneManifest, the following AppDelegate deep link callbacks are no longer called.

Solution

Airbridge Unreal SDK versions earlier than 4.10.0 do not provide a public interface for calling Airbridge deep links. Update Airbridge Unreal SDK to 4.10.0 or later, and then call Airbridge deep links from SceneDelegate.

1. Add Scene Manifest to Info.plist

Add the following Scene configuration to Info.plist in the Xcode project through UPL.

<?xml version="1.0" encoding="utf-8"?>
<root xmlns:android="http://schemas.android.com/apk/res/ios">
  <!-- init section is always evaluated once per architecture -->
  <init>
  </init>
	<iosPListUpdates>
		<addElements tag="dict" once="true">
			<key>UIApplicationSceneManifest</key>
			<dict>
				<key>UIApplicationSupportsMultipleScenes</key>
				<false/>
				<key>UISceneConfigurations</key>
				<dict>
					<key>UIWindowSceneSessionRoleApplication</key>
					<array>
						<dict>
							<key>UISceneConfigurationName</key>
							<string>Default Configuration</string>
							<key>UISceneDelegateClassName</key>
							<string>MyScene</string>
						</dict>
					</array>
				</dict>
			</dict>
		</addElements>
	</iosPListUpdates>
</root>

2. Create SceneDelegate and add deep link collection code

Create a SceneDelegate file that matches the UISceneDelegateClassName added to Scene Manifest.

@interface MyScene : UIResponder <UIWindowSceneDelegate>

@property (strong, nonatomic) UIWindow *window;

@end

@implementation MyScene

- (void)scene:(UIScene *)scene willConnectToSession:(UISceneSession *)session options:(UISceneConnectionOptions *)connectionOptions
{
    if ([NSThread isMainThread]) {
        if (![scene isKindOfClass:[UIWindowScene class]]) {
            return;
        }

        UIWindowScene *windowScene = (UIWindowScene *)scene;

        if (self.window.windowScene == windowScene) {
            [self.window makeKeyAndVisible];
            return;
        }

        UIWindow *sceneWindow = [[UIWindow alloc] initWithWindowScene:windowScene];

        if (self.window.rootViewController) {
            sceneWindow.rootViewController = self.window.rootViewController;
        }

        self.window = sceneWindow;
        [self.window makeKeyAndVisible];

        return;
    }

    dispatch_sync(dispatch_get_main_queue(), ^{
        if (![scene isKindOfClass:[UIWindowScene class]]) {
            return;
        }

        UIWindowScene *windowScene = (UIWindowScene *)scene;

        if (self.window.windowScene == windowScene) {
            [self.window makeKeyAndVisible];
            return;
        }

        UIWindow *sceneWindow = [[UIWindow alloc] initWithWindowScene:windowScene];

        if (self.window.rootViewController) {
            sceneWindow.rootViewController = self.window.rootViewController;
        }

        self.window = sceneWindow;
        [self.window makeKeyAndVisible];
    });
}

3. Add deep link collection code

Implement the following code in the created SceneDelegate to collect Airbridge deep links.

#import "AirbridgeUnrealDelegate.h"

- (void)scene:(UIScene *)scene willConnectToSession:(UISceneSession *)session options:(UISceneConnectionOptions *)connectionOptions
{
    /* ... Scene Initialize Codes ... */    

    if (![scene isKindOfClass:[UIWindowScene class]]) {
        [IOSAppDelegate trackDeeplinkWithConnectionOptions:connectionOptions];
        return;
    }

    [IOSAppDelegate trackDeeplinkWithConnectionOptions:connectionOptions];
}

- (void)scene:(UIScene *)scene openURLContexts:(NSSet<UIOpenURLContext *> *)URLContexts
{
    [IOSAppDelegate trackDeeplinkWithOpenURLContexts:URLContexts];
}

- (void)scene:(UIScene *)scene continueUserActivity:(NSUserActivity *)userActivity
{
    [IOSAppDelegate trackDeeplinkWithUserActivity:userActivity];
}

The domain of saved passwords appears as airbridge.io or abr.ge

Problem

Users may see the domain of passwords stored with the Password AutoFill feature as airbridge.io or abr.ge.

Cause

After setting up deep links for the Airbridge SDK, if you utilize the Password AutoFill feature, the domain is saved as the applinks domain of the Airbridge deep link, which is airbridge.io or abr.ge.

Solution

The problem can be solved by setting up the webcredentials domain used in the Password AutoFill.

Prepare the domain that will store the password.
Host the JSON below at https://YOUR_DOMAIN/.well-known/apple-app-site-association with Content-Type: application/json. Your prepared domain should be entered instead of YOUR_DOMAIN.

You can find the App ID Prefix and Bundle ID in the [Identifiers]>[YOUR_APP] menu of the Apple Developer Portal.

{
    "webcredentials": {
        "apps": ["YOUR_APP_ID_PREFIX.YOUR_BUNDLE_ID"]
    }
}

Navigate to [YOUR_PROJECT]>[Signing & Capabilities] in Xcode.
Click + Capability to add Associated Domains. Enter webcredentials:YOUR_DOMAIN in Associated Domains.

Upload Symbol Failed on Xcode

Problem

Upon uploading the app to the App Store, Xcode displays a warning message that a dSYM for the Airbridge framework was not included.

Cause

The Airbridge iOS SDK does not support dSYM.

Solution

The dSYM will be supported in the coming update. You may ignore this warning.

Android

A coroutine dependency error occurs during the build process

Issue

A coroutine dependency error occurs during the build process with the following message.

Text

java.lang.NoClassDefFoundError: kotlin/coroutines/AbstractCoroutineContextKey
    at java.base/java.lang.ClassLoader.defineClass1(Native Method)
    at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016)
  ...

Cause

If the kotlinx-coroutines-core library version is 1.3.5 or later, the kotlin-stdlib library version must be at a certain level or later.

Solution

Check whether the kotlin-stdlib library version is v.1.3.70 or later with the gradlew dependencies command. If the version is earlier than v.1.3.70, you need to update it.

Deeplink Opens generated through push notifications using the Braze SDK are not collected

Issue

Deeplink Open events that occur through the push notifications generated by the Braze SDK are not collected by Airbridge. Instead, the App Open event is collected.

Cause

The Airbridge Android SDK uses the dataString in the action and intent of the Activity to distinguish between Deeplink Open events and App Open events.When a user opens the app through a push notification using the Braze SDK, the app goes through NotificationTrampolineActivity. This activity handles push notifications, but the dataString is not included in its action and intent, preventing the SDK from determining if it’s a Deeplink Open event or an App Open event.

Solution

Add a custom Application class (CustomApplication.java) file as shown below.

package com.company.product;

import android.app.Activity;

import com.epicgames.ue4.GameApplication;

import org.jetbrains.annotations.Nullable;
import org.jetbrains.annotations.NotNull;

import co.ab180.airbridge.AirbridgeLifecycleIntegration;
import co.ab180.airbridge.ue.AirbridgeUnreal;

public class CustomApplication extends GameApplication {

    @Override
    public void onCreate() {
        super.onCreate();

        AirbridgeUnreal.setLifecycleIntegration(new AirbridgeLifecycleIntegration() {

            @Nullable
            @Override
            public String getDataString(@NotNull Activity activity) {
                if (activity.getClass().getName().equals("com.braze.push.NotificationTrampolineActivity")
                        && activity.getIntent() != null
                        && activity.getIntent().getExtras() != null
                ) {
                    return activity.getIntent().getExtras().getString("uri");
                }
                return null;
            }
        });
    }
}

package com.company.product;

import android.app.Activity;

import com.epicgames.unreal.GameApplication;

import org.jetbrains.annotations.Nullable;
import org.jetbrains.annotations.NotNull;

import co.ab180.airbridge.AirbridgeLifecycleIntegration;
import co.ab180.airbridge.ue.AirbridgeUnreal;

public class CustomApplication extends GameApplication {

    @Override
    public void onCreate() {
        super.onCreate();

        AirbridgeUnreal.setLifecycleIntegration(new AirbridgeLifecycleIntegration() {

            @Nullable
            @Override
            public String getDataString(@NotNull Activity activity) {
                if (activity.getClass().getName().equals("com.braze.push.NotificationTrampolineActivity")
                        && activity.getIntent() != null
                        && activity.getIntent().getExtras() != null
                ) {
                    return activity.getIntent().getExtras().getString("uri");
                }
                return null;
            }
        });
    }
}

Add a custom application class to the Android Manifest file using Unreal Plugin Language (UPL), as shown below.

<?xml version="1.0" encoding="utf-8"?>
<root xmlns:android="http://schemas.android.com/apk/res/android">
	
    <prebuildCopies>
        <copyDir src="$S(PluginDir)/..." dst="$S(BuildDir)/src/com/company/product" />
    </prebuildCopies>
    
	<androidManifestUpdates>
		<addAttribute tag="application" name="android:name" value="com.company.product.CustomApplication"/>
	</androidManifestUpdates>
	
</root>

The "Manifest merger failed" error occurrs during the build process

Issue

The “Manifest merger failed” error occurrs during the build process.

Cause

The Airbridge SDK’s AndroidManifest.xml includes rules to opt-out of backing up the Shared Preferences data. The purpose of this rule is to avoid retaining the same Airbridge settings during the reinstallation of the app so that new installs or reinstalls can be detected accurately.Merging Airbridge SDK backup rules with your app backup rules can cause conflicts.

Solution

Below are the opt-out rules defined in the Airbridge SDK.

<?xml version="1.0" encoding="utf-8"?>
<data-extraction-rules>
    <cloud-backup>
        <exclude domain="sharedpref" path="airbridge-internal" />
        <exclude domain="sharedpref" path="airbridge-install" />
        <exclude domain="sharedpref" path="airbridge-user-info" />
        <exclude domain="sharedpref" path="airbridge-user-alias" />
        <exclude domain="sharedpref" path="airbridge-user-attributes" />
        <exclude domain="sharedpref" path="airbridge-device-alias" />
        <exclude domain="database" path="airbridge.db" />
    </cloud-backup>
    <device-transfer>
        <exclude domain="sharedpref" path="airbridge-internal" />
        <exclude domain="sharedpref" path="airbridge-install" />
        <exclude domain="sharedpref" path="airbridge-user-info" />
        <exclude domain="sharedpref" path="airbridge-user-alias" />
        <exclude domain="sharedpref" path="airbridge-user-attributes" />
        <exclude domain="sharedpref" path="airbridge-device-alias" />
        <exclude domain="database" path="airbridge.db" />
    </device-transfer>
</data-extraction-rules>

<?xml version="1.0" encoding="utf-8"?>
<full-backup-content>
    <exclude domain="sharedpref" path="airbridge-internal" />
    <exclude domain="sharedpref" path="airbridge-install" />
    <exclude domain="sharedpref" path="airbridge-user-info" />
    <exclude domain="sharedpref" path="airbridge-user-alias" />
    <exclude domain="sharedpref" path="airbridge-user-attributes" />
    <exclude domain="sharedpref" path="airbridge-device-alias" />
    <exclude domain="database" path="airbridge.db" />
</full-backup-content>

Fix conflict with fullBackupContent=“string”

Adding android:fullBackupContent="string" to the AndroidManifest.xml may cause an error like the following.

Build Output

Manifest merger failed : Attribute application@fullBackupContent value=(string) from AndroidManifest.xml

To fix this error,

add xmlns:tools="http://schemas.android.com/tools" in the Platforms > Android > Extra Tags for <manifest> node to the Unreal Editor Project Settings window.
add tools:replace="android:fullBackupContent" in the Platforms > Android > Extra Tags for <application> node to the Unreal Editor Project Settings window.

Fix conflict with dataExtractionRules=“string resource”

Adding android:dataExtractionRules="string resource" to the AndroidManifest.xml may cause an error like the following.

Build Output

Manifest merger failed : Attribute application@dataExtractionRules value=(string resource) from AndroidManifest.xml

To fix this error,

add xmlns:tools="http://schemas.android.com/tools" to the Platforms > Android > Extra Tags for <manifest> node in the Unreal Editor Project Settings window.
add tools:replace="android:dataExtractionRules" to the Platforms > Android > Extra Tags for <application> node in the Unreal Editor Project Settings window.

Fix conflict with allowBackup=“false”

If you add android:allowBackup="false" in the AndroidManifest.xml, you might get the following error:

Build Output

Manifest merger failed : Attribute application@allowBackup value=(false) from AndroidManifest.xml:32:9-36
	is also present at [:airbridge] AndroidManifest.xml:27:9-35 value=(true).
	Suggestion: add 'tools:replace="android:allowBackup"' to <application> element at AndroidManifest.xml:30:5-250:19 to override.

To fix this error,

add xmlns:tools="http://schemas.android.com/tools" to the Platforms > Android > Extra Tags for <manifest> node in the Unreal Editor Project Settings window.
add tools:replace="android:allowBackup" to the Platforms > Android > Extra Tags for <application> node in the Unreal Editor Project Settings window.

If compileSdkVersion is l than 31

The android:dataExtractionRules has been added in API Level 31. Therefore, if the compileSdkVersion is lower than 31, an error like the following may occur.

Build Output

AndroidManifest.xml: AAPT: error: attribute android:dataExtractionRules not found.

To fix this error,

add xmlns:tools="http://schemas.android.com/tools" to the Platforms > Android > Extra Tags for <manifest> node in the Unreal Editor Project Settings window.
add tools:remove="android:dataExtractionRules" to the Platforms > Android > Extra Tags for <application> node in the Unreal Editor Project Settings window.

For more guidance, refer to the articles below.

Resolve Airbridge SDK backup rules merge conflict issue

Issue

If an Airbridge SDK backup rule and a backup rule for a different third-party SDK (e.g., AppsFlyer SDK) overlap, you will see the build error below.

Attribute application@fullBackupContent value=(@xml/appsflyer_backup_rules) from [com.appsflyer:af-android-sdk:6.6.1] AndroidManifest.xml:14:18-73
is also present at [io.airbridge:sdk-android:2.14.0] AndroidManifest.xml:27:18-78 value=(@xml/airbridge_auto_backup_rules).
Suggestion: add 'tools:replace="android:fullBackupContent"' to <application> element at AndroidManifest.xml:7:5-13:19 to override.

Cause

Overlapping of the Airbridge SDK backup rules and third-party SDK backup rules can cause build errors.

Solution

`backup_rules.xml` setup

Create a file (e.g., custom_backup_rules.xml) within the module directory.

Add the data backup rules defined by the Airbridge SDK as follows.

<?xml version="1.0" encoding="utf-8"?>
<full-backup-content>
    <!-- Airbridge Backup Rules -->
    <exclude domain="sharedpref" path="airbridge-internal" />
    <exclude domain="sharedpref" path="airbridge-install" />
    <exclude domain="sharedpref" path="airbridge-user-info" />
    <exclude domain="sharedpref" path="airbridge-user-alias" />
    <exclude domain="sharedpref" path="airbridge-user-attributes" />
    <exclude domain="sharedpref" path="airbridge-device-alias" />
    <exclude domain="database" path="airbridge.db" />

    <!-- Appsflyer Backup Rules -->
    <exclude domain="sharedpref" path="appsflyer-data"/>
 
	<!-- Your Custom Backup Rules -->
</full-backup-content>

Using the Unreal Plugin Language (UPL), copy the file into your res/xml folder as follows.

<?xml version="1.0" encoding="utf-8"?>
<root xmlns:android="http://schemas.android.com/apk/res/android">
    ...
    <resourceCopies>
        <copyFile src="{YOUR_XML_BACKUP_RULES_PATH}" dst="$S(BuildDir)/res/xml/custom_backup_rules.xml" />
        ...
    </resourceCopies>
    ...
</root>

`data_extraction_rules.xml` setup

Create a file (e.g., custom_data_extraction_rules.xml) within the module directory.

Add the data backup rules defined by the Airbridge SDK as follows.

<?xml version="1.0" encoding="utf-8"?>
<data-extraction-rules>
    <cloud-backup>
        <!-- Airbridge Backup Rules -->
        <exclude domain="sharedpref" path="airbridge-internal" />
        <exclude domain="sharedpref" path="airbridge-install" />
        <exclude domain="sharedpref" path="airbridge-user-info" />
        <exclude domain="sharedpref" path="airbridge-user-alias" />
        <exclude domain="sharedpref" path="airbridge-user-attributes" />
        <exclude domain="sharedpref" path="airbridge-device-alias" />
        <exclude domain="database" path="airbridge.db" />

        <!-- Appsflyer Backup Rules -->
        <exclude domain="sharedpref" path="appsflyer-data"/>

	    <!-- Your Custom Backup Rules -->
    </cloud-backup>
    <device-transfer>
        <!-- Airbridge Backup Rules -->
        <exclude domain="sharedpref" path="airbridge-internal" />
        <exclude domain="sharedpref" path="airbridge-install" />
        <exclude domain="sharedpref" path="airbridge-user-info" />
        <exclude domain="sharedpref" path="airbridge-user-alias" />
        <exclude domain="sharedpref" path="airbridge-user-attributes" />
        <exclude domain="sharedpref" path="airbridge-device-alias" />
        <exclude domain="database" path="airbridge.db" />

        <!-- Appsflyer Backup Rules -->
        <exclude domain="sharedpref" path="appsflyer-data"/>

	    <!-- Your Custom Backup Rules -->
    </device-transfer>
</data-extraction-rules>

Using the Unreal Plugin Language (UPL), copy the file into your res/xml folder as follows.

<?xml version="1.0" encoding="utf-8"?>
<root xmlns:android="http://schemas.android.com/apk/res/android">
    ...
    <resourceCopies>
        <copyFile src="{YOUR_XML_BACKUP_RULES_PATH}" dst="$S(BuildDir)/res/xml/custom_data_extraction_rule.xml" />
        ...
    </resourceCopies>
    ...
</root>

`AndroidManifest.xml` setup

In the Unreal Editor Project Settings window, add the following element to the Platforms - Android > Advanced APK Packaging > Extra Tags for <manifest> node.

xmlns:tools="http://schemas.android.com/tools"

In the Unreal Editor Project Settings window, add the following elements to the Platforms - Android > Advanced APK Packaging > Extra Tags for <application> node.

android:allowBackup="true"
android:fullBackupContent="@xml/custom_backup_rules"
android:dataExtractionRules="@xml/custom_data_extraction_rules"
tools:replace="android:fullBackupContent, android:dataExtractionRules"

For more guidance, refer to the articles below.

GAID is collected as 00000000-0000-0000-0000-000000000000

Issue

GAID is being collected as 00000000-0000-0000-0000-000000000000 even though LAT (Limited Ad Tracking) is deactivated.

Cause

The AD_ID permission has been excluded due to other third-party libraries.

Solution

Add AD_ID permission.

<manifest ...>
  ...
  <uses-permission android:name="com.google.android.gms.permission.AD_ID" />
  ...
</manifest>

Issue

When uploading your app to Google Play Console, you may receive the following warning or rejection messages:

“Your app doesn’t support 16 KB page size”
“16 KB page size compatibility required”
App upload is rejected or displayed in a warning state

This is due to Google Play policy requirements that apps targeting Android 15 (API level 35) or higher must support 16KB page size.

Cause

To support 16 KB page sizes, the entire app (APK/AAB) must be packaged with 16 KB zipalign to pass Google Play policy.If the APK/AAB is not built with 16 KB zipalign:

You will receive warning or rejection messages when uploading to Google Play Console
Uploads will be completely blocked after November 1, 2025
The app may not work properly on 16KB page size devices in the future

Known Issue in the Airbridge SDK: PT_GNU_RELRO AlignmentThe Airbridge SDK has supported 16 KB page sizes since v4.6. However, in versions built with NDK r21, the LOAD segments of the native libraries (.so) are aligned to the 16 KB boundary, but the PT_GNU_RELRO segment is not.

App behavior is not affected. The app runs normally on 16 KB page size devices.
However, Google Play Console may display a 16 KB page size warning when you upload your app.
Alignment check tools such as Android Studio lint, APK Analyzer, and check_elf_alignment.sh may also report this as a warning.

This issue was resolved by upgrading the SDK build toolchain to NDK r27, and 16 KB page size support has been verified after the fix. Refer to the table below for the minimum version with 16 KB support and the recommended version for each platform.

Platform	Minimum Version with 16 KB Support	Recommended Version (PT_GNU_RELRO issue fixed)
Android	v4.6	v4.9.4
React Native	v4.6	v4.9.0
Cordova Ionic	v4.4.1	x (support planned)
Flutter	v4.6	v4.9.0
Expo	v4.6	v4.9.0
Unity	v4.6	v4.9.2
Unreal	v4.6	v4.9.0

Solution

Step 1: Check Airbridge SDK VersionCompare the Airbridge SDK version you are using against the table above.

If you are using a version lower than the Minimum Version with 16 KB Support: 16 KB page sizes are not supported. Be sure to update.
If you are using a version at or above the Minimum Version with 16 KB Support but below the Recommended Version: The PT_GNU_RELRO alignment issue described above may cause Google Play Console to keep showing the warning. App behavior is not affected, but to resolve the warning, update to the Recommended Version or later.

Step 2: Check and Configure Android Gradle Plugin (AGP) VersionCheck your project’s current AGP version.If using AGP 8.5.1 or higher:

16KB zipalign is automatically applied without any additional configuration.
Proceed directly to Step 3.

If using AGP 8.5.0 or lower:

Option A: Upgrade AGP to 8.5.1 or higher

Option B: Keep current AGP version + Add configuration

android {
    ...
    packagingOptions {
        jniLibs {
            useLegacyPackaging true
        }
    }
}

Step 3: Rebuild and Verify the AppAfter changing the configuration, perform a clean build of your app.Step 4: Verify 16KB zipalign ApplicationVerify that the built APK/AAB is properly 16KB zipaligned.

​iOS

​Symptoms

​Cause

​Solution

​1. Add Scene Manifest to Info.plist

​2. Create SceneDelegate and add deep link collection code

​3. Add deep link collection code

​Problem

​Cause

​Solution

​Problem

​Cause

​Solution

​Android

​Issue

​Cause

​Solution

​Issue

​Cause

​Solution

​Issue

​Cause

​Solution

Fix conflict with fullBackupContent=“string”

Fix conflict with dataExtractionRules=“string resource”

Fix conflict with allowBackup=“false”

If compileSdkVersion is l than 31

​Issue

​Cause

​Solution

backup_rules.xml setup

data_extraction_rules.xml setup

AndroidManifest.xml setup

​Issue

​Cause

​Solution

​Issue

​Cause

​Solution

iOS

Symptoms

Cause

Solution

1. Add Scene Manifest to Info.plist

2. Create SceneDelegate and add deep link collection code

3. Add deep link collection code

Problem

Cause

Solution

Problem

Cause

Solution

Android

Issue

Cause

Solution

Issue

Cause

Solution

Issue

Cause

Solution

Issue

Cause

Solution

`backup_rules.xml` setup

`data_extraction_rules.xml` setup

`AndroidManifest.xml` setup

Issue

Cause

Solution

Issue

Cause

Solution