BillingClient Dependency
BillingClient Dependency
If you install the Airbridge SDK manually, you may encounter a compilation error due to a
BillingClient dependency issue.Starting from Airbridge SDK 2.26.1, a feature for collecting In-App purchase history has been added. To accommodate this, the SDK sets the In-App purchase library dependency as compileOnly, which does not cause issues during Gradle builds. However, when installed manually, a missing dependency may lead to compilation errors.To resolve this issue, please refer to the following instructions.Ad ID permission
Ad ID permission
GAID is being collected as 00000000-0000-0000-0000-000000000000 even though LAT (Limited Ad Tracking) is deactivated.For more details, refer to the Google Play Services document.
- Open the AndroidManifest.xml file.
- Follow the method below to add the
com.google.android.gms.permission.AD_IDpermission.
Braze push notification
Braze push notification
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.deeplink.page
deeplink.page
Although the
deeplink.page has been deprecated in the Airbridge Android SDK v.2.21.1, for Airbridge Android SDK v2.21.0 or earlier, you can set up the intent-filter by following the steps below.- Open the
AndroidManifest.xmlfile. - Add the following
intent-filterto theactivitythat will process deep links.
Dependencies
Dependencies
java.lang.NoClassDefFoundError: kotlin/coroutines/AbstractCoroutineContextKey Error
gradlew dependencies command.Auto Backup
Auto Backup
The Airbridge SDK’s
AndroidManifest.xml includes rules to opt out of backing up the Shared Preferences data. This is done to prevent keeping the same Airbridge settings during reinstallation, ensuring that new installations or reinstalls can be detected accurately.To merge the Airbridge SDK backup rules with your app backup rules and prevent conflicts, refer to the following instructions.Below are the opt-out rules defined in the Airbridge SDK.Fix confilict with fullBackupContent="string"
Fix confilict with fullBackupContent="string"
If you add To fix this error, add
android:fullBackupContent="string" in the AndroidManifest.xml, you might get the following error:Build Output
tools:replace="android:fullBackupContent" in the <application> tag in the AndroidManifest.xml file.Fix conflict with dataExtractionRules="string resource"
Fix conflict with dataExtractionRules="string resource"
If you add To fix this error, add
android:dataExtractionRules="string resource" in the AndroidManifest.xml, you might get the following error:Build Output
tools:replace="android:dataExtractionRules" in the <application> tag in the AndroidManifest.xml file.Fix conflict with allowBackup="false"
Fix conflict with allowBackup="false"
If you add To fix this error, add
android:allowBackup="false" in the AndroidManifest.xml, you might get the following error:Build Output
tools:replace="android:allowBackup" in the <application> tag in the AndroidManifest.xml file.If compileSdkVersion is less than 31
If compileSdkVersion is less than 31
Since the android:dataExtractionRules feature was added from API Level 31, you might get the following error if compileSdkVersion is less than 31:To fix this error, add
Build Output
tools:remove="android:dataExtractionRules" in the <application> tag in the AndroidManifest.xml file.Resolve Airbridge SDK backup rules merge conflict issue
Resolve Airbridge SDK backup rules merge conflict issue
If you are experiencing build errors caused by overlapping of the Airbridge SDK backup rules and third-party SDK backup rules, please refer to the workaround below.e.g) If you have an Airbridge SDK backup rule and an Appsflyer SDK backup rule that overlap, you will see the build error below.To resolve this issue, please set up as follows.
backup_rules.xml setup
backup_rules.xml setup
- Create a
src/main/res/xmlfolder. - Within the created xml folder, create a file (e.g.
custom_backup_rules.xml). - Add the data backup rules defined in the Airbridge SDK as follows.
data_extraction_rules.xml setup
data_extraction_rules.xml setup
NoteThe data_extraction_rules.xml setting is required for Airbridge Android SDK v2.27.1 and above.
- Within the created xml folder, create a file (e.g.
custom_data_extraction_rules.xml). - Add the data backup rules defined in the Airbridge SDK as follows.
AndroidManifest.xml setup
AndroidManifest.xml setup
Airbridge Android SDK v2.27.1 or above
Airbridge Android SDK version less than v2.27.1
Double brace initialization issue
Double brace initialization issue