> ## Documentation Index
> Fetch the complete documentation index at: https://help.airbridge.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting - Unity SDK

## iOS

<Accordion title="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](https://developer.apple.com/documentation/security/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.

  1. Prepare the domain that will store the password.
  2. 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](https://developer.apple.com/account/resources).

  ```json lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
  {
      "webcredentials": {
          "apps": ["YOUR_APP_ID_PREFIX.YOUR_BUNDLE_ID"]
      }
  }
  ```

  3. Navigate to **\[YOUR\_PROJECT]>\[Signing & Capabilities]** in Xcode.
  4. Click **+ Capability** to add Associated Domains. Enter `webcredentials:YOUR_DOMAIN` in Associated Domains.
</Accordion>

## Android

<AccordionGroup>
  <Accordion title="A coroutine dependency error occurs during the build process">
    #### Issue

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

    ```html Text lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    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](https://github.com/Kotlin/kotlinx.coroutines/issues/1879).

    #### 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.
  </Accordion>

  <Accordion title="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.

    <CodeGroup>
      ```java Java lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
      package com.company.product;

      import android.app.Activity;
      import android.app.Application;

      import androidx.annotation.NonNull;
      import androidx.annotation.Nullable;

      import co.ab180.airbridge.AirbridgeLifecycleIntegration;
      import co.ab180.airbridge.unity.AirbridgeUnity;

      public class CustomApplication extends Application {

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

              AirbridgeUnity.setLifecycleIntegration(new AirbridgeLifecycleIntegration() {

                  @Nullable
                  @Override
                  public String getDataString(@NonNull 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;
                  }
              });
          }
      }
      ```
    </CodeGroup>

    Add the custom Application class to the Custom Main Manifest (`Assets/Plugins/Android/AndroidManifest.xml`) file as shown below.

    ```xml lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    <?xml version="1.0" encoding="utf-8"?>
    <manifest ...>
      
      <application android:name="com.company.product.CustomApplication"
        android:theme="@style/UnityThemeSelector"
        android:icon="@mipmap/app_icon"
        android:label="@string/app_name">

        ...

      </application>
    </manifest>
    ```
  </Accordion>

  <Accordion title="The &#x22;Manifest merger failed&#x22; error occurs during the build process">
    #### Issue

    The "Manifest merger failed" error occurs 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.

    <CodeGroup>
      ```xml Backup on Android 12 or later lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
      <?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 Backup on Android 11 and earlier lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
      <?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>
      ```
    </CodeGroup>

    ##### Fix conflict with fullBackupContent="string"

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

    ```html Build Output lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    Manifest merger failed : Attribute application@fullBackupContent value=(string) from AndroidManifest.xml
    ```

    To fix this error,

    * add `xmlns:tools="http://schemas.android.com/tools"` to the `<manifest>` tag
    * add `tools:replace="android:fullBackupContent"` to the `<application>` tag

    in the Custom Main Manifest(`Assets/Plugins/Android/AndroidManifest.xml`) file.

    ##### Fix conflict with dataExtractionRules="string resource"

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

    ```html Build Output lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    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 `<manifest>` tag
    * add `tools:replace="android:dataExtractionRules"` to the `<application>` tag

    in the Custom Main Manifest(`Assets/Plugins/Android/AndroidManifest.xml`) file.

    ##### Fix conflict with allowBackup="false"

    Adding `android:allowBackup="false"` to the `AndroidManifest.xml` file may cause an error like the following.

    ```html Build Output lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    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 `<manifest>` tag
    * add `tools:replace="android:allowBackup"` to the `<application>` tag

    in the Custom Main Manifest(`Assets/Plugins/Android/AndroidManifest.xml`) file.

    ##### If compileSdkVersion is lower 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.

    ```html Build Output lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    AndroidManifest.xml: AAPT: error: attribute android:dataExtractionRules not found.
    ```

    To fix this error,

    * add `xmlns:tools="http://schemas.android.com/tools"` to the `<manifest>` tag
    * add `tools:remove="android:dataExtractionRules"` to the `<application>` tag

    in the Custom Main Manifest(`Assets/Plugins/Android/AndroidManifest.xml`) file.

    For more guidance, refer to the articles below.

    * [Android Developers Guide](https://developer.android.com/identity/data/autobackup)
    * [Airbridge Developer Guide](https://airbridge.readme.io/page/auto-backup-%EC%A4%91%EB%B3%B5-%EB%AC%B8%EC%A0%9C-%ED%95%B4%EA%B2%B0-%EA%B0%80%EC%9D%B4%EB%93%9C)
  </Accordion>

  <Accordion title="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.

    ```html lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    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

    1. Create an Android Library project (`Assets/Plugins/Android/res.androidlib`) to store your resource files.
    2. Add an `AndroidManifest.xml` file in the created Android Library Project as follows.

    ```xml lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    <?xml version="1.0" encoding="utf-8"?>
    <manifest xmlns:android="http://schemas.android.com/apk/res/android"
              package="custom.android.res"
              android:versionCode="1"
              android:versionName="1.0">
    </manifest>
    ```

    3. Create a `res/xml` folder inside the created Android Library Project.
    4. Create a file (e.g., `custom_backup_rules.xml`) within the new xml folder.
    5. Add the data backup rules defined by the Airbridge SDK as follows.

    ```xml lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    <?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>
    ```

    ##### `data_extraction_rules.xml` setup

    1. Create a file (e.g., `custom_data_extraction_rules.xml`) within the new xml folder.
    2. Add the data backup rules defined by the Airbridge SDK as follows.

    ```xml lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    <?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>
    ```

    ##### `AndroidManifest.xml` setup

    Apply the data backup rules to the Android App Manifest file (`Assets/Plugins/Android/AndroidManifest.xml`) as follows.

    ```xml lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    <manifest
        ...
        xmlns:tools="http://schemas.android.com/tools">

        <application
            ...
            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.

    * [Import an Android Library Project](https://docs.unity3d.com/2022.3/Documentation/Manual/android-library-project-import.html)
    * [Override the Android App Manifest](https://docs.unity3d.com/2022.3/Documentation/Manual/overriding-android-manifest.html)
  </Accordion>

  <Accordion title="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.

    ```xml lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    <manifest ...>
      ...
      <uses-permission android:name="com.google.android.gms.permission.AD_ID" />
      ...
    </manifest>
    ```
  </Accordion>

  <Accordion title="Warnings or rejections related to 16KB page size occur when uploading to Google Play">
    ### **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 Alignment**

    The 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 Version**

    Compare 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) Version**

    Check 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

    ```groovy lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
    android {
        ...
        packagingOptions {
            jniLibs {
                useLegacyPackaging true
            }
        }
    }
    ```

    **Step 3: Rebuild and Verify the App**

    After changing the configuration, perform a clean build of your app.

    **Step 4: Verify 16KB zipalign Application**

    Verify that the built APK/AAB is properly 16KB zipaligned.
  </Accordion>
</AccordionGroup>

<link rel="alternate" hrefLang="en" href="https://help.airbridge.io/en/developers/troubleshooting-unity-sdk-v4" />

<link rel="alternate" hrefLang="ko" href="https://help.airbridge.io/ko/developers/troubleshooting-unity-sdk-v4" />