iOS
[Xcode 27] SceneDelegate Migration Required — Additional Setup Needed for Airbridge Deep Links
[Xcode 27] SceneDelegate Migration Required — Additional Setup Needed for Airbridge Deep Links
AttentionThis troubleshooting guide is for customers who need to migrate an existing AppDelegate-based app to the
SceneDelegate (UIScene lifecycle).Problem
- When you run an app built with Xcode 27, the app may not run properly.
- Airbridge deep link events are not collected even when the app is opened through a scheme deep link or Universal Link.
- The app does not work even though the code was added using the
AppDelegateapproach shown in the Initialize SDK and Set up deep linking developer guide examples.
Cause
Apple is moving the app lifecycle from theUIApplicationDelegate-only AppDelegate model to the UIScene-based SceneDelegate model, and adopting the Scene lifecycle has effectively become required in the latest Xcode and iOS environments.When an app adopts the Scene lifecycle through UIApplicationSceneManifest, the following AppDelegate deep link callbacks are no longer called.Solution
The required steps depend on the Unity Engine and Airbridge SDK versions.Starting with the Unity Engine versions listed below, Unity generatesUnityScene when creating an Xcode project.Unity versions that support UnityScene
Use the listed version or later for each Unity release series.If you are using a version that does not support
UnityScene, you need to add a separate UIScene.Versions that do not support UnityScene
- Airbridge SDK earlier than 4.10.0
- Airbridge SDK 4.10.0 or later
In the
SceneDelegate file where you added a UIScene in Unity, call the public deep link interface in AUAppDelegate.h.Versions that support UnityScene
- Airbridge SDK earlier than 4.11.0
- Airbridge SDK 4.10.0 or later
In the
UnityScene file of the Xcode project generated by Unity, call the public deep link interface in AUAppDelegate.h.The domain of saved passwords appears as airbridge.io or abr.ge
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 feature asairbridge.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 isairbridge.io or abr.ge.Solution
The problem can be solved by setting up the webcredentials domain used in the Password AutoFill.- Prepare the domain that will store the password.
- Host the JSON below at
https://YOUR_DOMAIN/.well-known/apple-app-site-associationwithContent-Type: application/json. Your prepared domain should be entered instead ofYOUR_DOMAIN.
- Navigate to [YOUR_PROJECT]>[Signing & Capabilities] in Xcode.
- Click + Capability to add Associated Domains. Enter
webcredentials:YOUR_DOMAINin Associated Domains.
The Upload Symbol Failed warning appears in Xcode
The Upload Symbol Failed warning appears in Xcode
Android
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 generated through push notifications using the Braze SDK are not collected
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 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 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.Assets/Plugins/Android/AndroidManifest.xml) file as shown below.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
Assets/Plugins/Android/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
Assets/Plugins/Android/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
Assets/Plugins/Android/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
Assets/Plugins/Android/AndroidManifest.xml) file.For more guidance, refer to the articles below.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
backup_rules.xml setup
- Create an Android Library project (
Assets/Plugins/Android/res.androidlib) to store your resource files. - Add an
AndroidManifest.xmlfile in the created Android Library Project as follows.
- Create a
res/xmlfolder inside the created Android Library Project. - Create a file (e.g.,
custom_backup_rules.xml) within the new xml folder. - Add the data backup rules defined by the Airbridge SDK as follows.
data_extraction_rules.xml setup
- Create a file (e.g.,
custom_data_extraction_rules.xml) within the new xml folder. - Add the data backup rules defined by the Airbridge SDK as follows.
AndroidManifest.xml setup
Apply the data backup rules to the Android App Manifest file (Assets/Plugins/Android/AndroidManifest.xml) as follows.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.