Users may see the domain of passwords stored with the Password AutoFill feature as airbridge.io or abr.ge.
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.
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.
{
"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.
A coroutine dependency error occurs during the build process with the following message.
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)
...
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 1.3.70 or later with the gradlew dependencies
command. If the version is earlier than 1.3.70, you need to update it.
Deep link execution (Deeplink Open) events are not collected when using the Braze SDK for push notifications. Instead, the open event is collected.
The Airbridge Android SDK distinguishes the deep link execution event and the open event based on the dataString found in the activity's action and intent. When the app is launched through a push notification using the Braze SDK, NotificationTrampolineActivity
is used. When an app is launched through a push notification using the Braze SDK, dataString cannot be verified from the action and intent of the NotificationTrampolineActivity
. As a result, it is impossible to distinguish between the deep link execution event and the open event.
import co.ab180.airbridge.flutter.AirbridgeFlutter
...
AirbridgeFlutter.setLifecycleIntegration { activity ->
return@setLifecycleIntegration activity
.takeIf { it.javaClass.name == "com.braze.push.NotificationTrampolineActivity" }
?.run { intent?.extras?.getString("uri") }
}
import co.ab180.airbridge.flutter.AirbridgeFlutter;
import co.ab180.airbridge.flutter.common.AirbridgeLifecycleIntegration;
...
AirbridgeFlutter.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;
}
});
The "Manifest merger failed" error occurred during the build process.
The Airbridge SDK's AndroidManifest.xml
includes rules to opt-out of backing up the Shared Preferences data. This is done to avoid retaining the same Airbridge settings during reinstallation so that new installs or re-installs 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.
<?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>
If you add android:fullBackupContent="string"
in the AndroidManifest.xml
, you might get the following error:
Manifest merger failed : Attribute application@fullBackupContent value=(string) from AndroidManifest.xml
To fix this error, add tools:replace="android:fullBackupContent"
in the <application>
tag in the AndroidManifest.xml
file.
If you add android:dataExtractionRules="string resource"
in the AndroidManifest.xml
, you might get the following error:
Manifest merger failed : Attribute application@dataExtractionRules value=(string resource) from AndroidManifest.xml
To fix this error, add tools:replace="android:dataExtractionRules"
in the <application>
tag in the AndroidManifest.xml
file.
If you add android:allowBackup="false"
in the AndroidManifest.xml
, you might get the following error:
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 tools:replace="android:allowBackup"
in the <application>
tag in the AndroidManifest.xml
file.
Since the android:dataExtractionRules feature was added from API Level 31, you might get the following error if compileSdkVersion is less than 31:
AndroidManifest.xml: AAPT: error: attribute android:dataExtractionRules not found.
To fix this error, add tools:remove="android:dataExtractionRules"
in the <application>
tag in the AndroidManifest.xml
file.
For more guidance, refer to the articles below.
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.
<manifest ...>
...
<uses-permission android:name="com.google.android.gms.permission.AD_ID" />
...
</manifest>
Was this page helpful?