A coroutine dependency error occurs during the build process
A coroutine dependency error occurs during the build process
Issue
A coroutine dependency error occurs during the build process with the following message.Text
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 thegradlew dependencies command. If the version is earlier than v.1.3.70, you need to update it.Deeplink Opens that occur through push notifications using the Braze SDK are not collected
Deeplink Opens that occur 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 thedataString 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.Solution
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 "Manifest merger failed" error occurs during the build process
Issue
The “Manifest merger failed” error occurs during the build process.Cause
The Airbridge SDK’sAndroidManifest.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.Fix conflict with fullBackupContent=“string”
Addingandroid:fullBackupContent="string" to the AndroidManifest.xml file may cause an error like the following.Build Output
- add
xmlns:tools="http://schemas.android.com/tools"to the<manifest>tag - add
tools:replace="android:fullBackupContent"to the<application>tag
AndroidManifest.xml file.Fix conflict with dataExtractionRules=“string resource”
Addingandroid:dataExtractionRules="string resource" to the AndroidManifest.xml file may cause an error like the following.Build Output
- add
xmlns:tools="http://schemas.android.com/tools"to the<manifest>tag - add
tools:replace="android:dataExtractionRules"to the<application>tag
AndroidManifest.xml file.Fix conflict with allowBackup=“false”
Addingandroid:allowBackup="false" to the AndroidManifest.xml file may cause an error like the following.Build Output
- add
xmlns:tools="http://schemas.android.com/tools"to the<manifest>tag - add
tools:replace="android:allowBackup"to the<application>tag
AndroidManifest.xml file.If compileSdkVersion is lower than 31
Theandroid: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
- add
xmlns:tools="http://schemas.android.com/tools"to the<manifest>tag - add
tools:remove="android:dataExtractionRules"to the<application>tag
AndroidManifest.xml file.For more guidance, refer to the articles below.Airbridge SDK Backup Rule Configuration (SDK below 4.9.0)
Airbridge SDK Backup Rule Configuration (SDK below 4.9.0)
NoticeAirbridge 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.
Why Configuration is Needed
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.Configuration Methods
If android:allowBackup=”…” is included- Add
android:allowBackupto thetools:replaceattribute of the<application>tag inAndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.
- Add
android:dataExtractionRulesto thetools:replaceattribute of the<application>tag inAndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.
- 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)
- Add
android:fullBackupContentto thetools:replaceattribute of the<application>tag inAndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.
- 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 thatandroid:fullBackupContent="false"means there is no backup rules file, so you do not need to add the rules below.
Caution
When adding values to thetools: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.Resolve Airbridge SDK backup rules merge conflict issue
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.Cause
Overlapping of the Airbridge SDK backup rules and third-party SDK backup rules can cause build errors.Solution
Follow these steps to consolidate all SDK backup rules into one file.- 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
- For Android 11 and below:
- For Android 12 and above:
data_extraction_rules.xml
- Add
android:allowBackupto thetools:replaceattribute of the<application>tag inAndroidManifest.xml. If there are other values, separate them with a comma (,). If there are no other values, do not use a comma.
Caution
When adding values to thetools: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 collected as 00000000-0000-0000-0000-000000000000
GAID is collected as 00000000-0000-0000-0000-000000000000
16KB page size or NDK version warnings occur when uploading to Google Play
16KB page size or NDK version warnings occur when uploading to Google Play
Symptoms
When uploading your app to Google Play Console, one of the following warnings may be displayed. The cause differs depending on the warning message, so first check which warning you received.A. 16KB page size not supported- “Your app doesn’t support 16 KB page size”
- “16 KB page size compatibility required”
- The memory page size item in App Bundle Explorer shows “Does not support 16 KB”.
- The 16KB page size warning keeps appearing even though you are using an SDK version that supports 16KB.
Cause
Google Play requires apps targeting Android 15 (API level 35) or higher to support 16KB page sizes on 64-bit devices. A warning is displayed if the native libraries (.so) included in the app are not built with 16KB alignment, or if the NDK version used to build them is lower than Google Play’s check criteria.Depending on the version, the native libraries of the Airbridge SDK are subject to the following warnings.Using v4.12.0 or later resolves all three warnings above.Starting with v4.12.0, the Airbridge Android SDK is built with NDK r29 (29.0.14206865). Regardless of which warning you received, update to the recommended version.
Solution
Step 1: Check and update the Airbridge SDK version
Compare the Airbridge SDK version for your platform against the table below.- If you are using a version below the
Minimum version with 16KB support: 16KB page sizes are not supported. Be sure to update. - If you are using a version at or above the
Minimum version with 16KB supportbut below thePT_GNU_RELRO issue fixedversion: Warning B or C may be displayed. - If you are using a version at or above the
PT_GNU_RELRO issue fixedversion but below theRecommended version: Warning C may be displayed.
Recommended version or later. For platforms where the Recommended version has not been released yet, use the PT_GNU_RELRO issue fixed version or later.Step 2: Check and configure the Android Gradle Plugin (AGP) version
Check your project’s AGP version.If using AGP 8.5.1 or higher- 16KB zipalign is automatically applied without additional configuration.
- Proceed to Step 3.
- Option A: Upgrade AGP to 8.5.1 or higher.
- Option B: Keep your current AGP version and add the configuration below.
Step 3: Clean build
After changing the configuration, perform a clean build of your app.Step 4: Verify 16KB zipalign
Verify that the built APK is packaged with 16KB zipalign.How to check which libraries trigger the warning
Warning C may also be displayed because of native libraries from other SDKs included in your app, not just the Airbridge SDK. Check whether the following file is included in the.so list shown in the Play Console warning.- Airbridge SDK native library:
libairbridgelib.so
llvm-readelf, which is included in the NDK.FAQ
Q. Will my app upload be blocked if warning C is displayed?Warning C is currently displayed as a technical quality recommendation in Play Console, and you can still upload your app. However, Google Play plans to block the release of app updates that do not support 16KB page sizes starting February 1, 2027, so update to the recommended version in advance.Q. Does app behavior change while warning B or C is displayed?- Warning B: App behavior is not affected. The app runs normally on 16KB page size devices.
- Warning C: To resolve the warning, updating to v4.12.0 or later is recommended.
check_elf_alignment.sh may also display warnings for the same reasons. Updating to the recommended version according to the solution above resolves them.An error occurs when setting android:allowBackup="false"
An error occurs when setting android:allowBackup="false"
Issue
When settingandroid:allowBackup="false", the following build error appears.Cause
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.Solution
To resolve this issue, remove all spaces within thetools:replace attribute value and perform a Clean Build.