Troubleshooting - Android SDK

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

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.

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

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 an activity called 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.

The problem can be solved using the code snippet below for Airbridge Android SDK versions v2.21.5 and later.

The "Manifest merger failed" error occurs during the build process.

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.

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

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

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 AndroidManifest.xml file.

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

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 AndroidManifest.xml file.

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

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 AndroidManifest.xml file.

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.

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 AndroidManifest.xml file.

For more guidance, refer to the articles below.

• Android Developers Guide

• Airbridge Developer Guide

Notice

Airbridge Android SDK 4.9.0 and above do not require backup rule configuration. Only proceed with this step if you are using a version below 4.9.0.

The Airbridge Android SDK requires certain data to be excluded from backup to ensure accurate reinstall detection. For SDK versions below 4.9.0, this must be configured manually.

If android:allowBackup="..." is included

1. Add android:allowBackup to the tools:replace attribute of the <application> tag in AndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.

   <application android:allowBackup="..." tools:replace="...,android:allowBackup" ...>

If android:dataExtractionRules="..." is included

1. Add android:dataExtractionRules to the tools:replace attribute of the <application> tag in AndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.

   <application android:dataExtractionRules="..." tools:replace="...,android:dataExtractionRules" ...>

2. Specify the backup rules file in android:dataExtractionRules="...". Add Airbridge exclusion rules to the backup rules file. (e.g., res/xml/data_extraction_rules.xml)

   <?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>

If android:fullBackupContent="..." is included

1. Add android:fullBackupContent to the tools:replace attribute of the <application> tag in AndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.

   <application android:fullBackupContent="..." tools:replace="...,android:fullBackupContent" ...>

2. Specify the backup rules file in android:fullBackupContent="...". Add Airbridge exclusion rules to the backup rules file. (e.g., res/xml/backup_rules.xml) Note that android:fullBackupContent="false" means there is no backup rules file, so you do not need to add the rules below.

   <?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>

When adding values to the tools:replace attribute of the <application> tag, if there is a space after the comma (,), it may cause build errors in some Android Gradle Plugin (AGP) versions. Please be aware.

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.

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

Follow these steps to consolidate all SDK backup rules into one file.

1. Create a backup rules file under the res/xml folder. If a file already exists, only add the Airbridge content.

   • For Android 11 and below: backup_rules.xml

     <?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>

   • For Android 12 and above: data_extraction_rules.xml

     <?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>

2. Add android:allowBackup to the tools:replace attribute of the <application> tag in AndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.

   <application android:fullBackupContent="@xml/custom_backup_rules" android:dataExtractionRules="@xml/custom_data_extraction_rules" tools:replace="android:fullBackupContent,android:dataExtractionRules">

When adding values to the tools:replace attribute of the <application> tag, if there is a space after the comma (,), it may cause build errors in some Android Gradle Plugin (AGP) versions. Please be aware.

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

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

Add AD_ID permission.

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.

Airbridge SDK supports 16KB page size from the following versions:

However, SDK support alone is not sufficient. The entire app (APK/AAB) must be packaged with 16KB zipalign to pass Google Play policy.

If APK/AAB is not built with 16KB 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

Step 1: Check Airbridge SDK Version

First, verify that your Airbridge SDK version supports 16KB. If you are using an older version, you must update to the latest version.

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

  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.

When setting android:allowBackup="false", the following build error appears.

This issue may occur due to differences in the Manifest Merger's parsing behavior depending on the version of the Android Gradle Plugin (AGP).

In certain AGP versions, the parser fails to automatically trim whitespace following a comma (,) when interpreting the tools:replace="..." attribute in AndroidManifest.xml. In this scenario, the string containing the whitespace is incorrectly recognized as a distinct, invalid attribute key. Consequently, the attribute replacement rules may fail to apply, or build errors may occur due to duplicate declarations.

To resolve this issue, remove all spaces within the tools:replace attribute value and perform a Clean Build.