When unexpected behavior or errors occur after integrating the Airbridge SDK, debug logs are essential for accurate problem diagnosis. This guide explains how to check and save Airbridge debug logs on each platform.

To check debug logs, you must first set the logLevel when initializing the Airbridge SDK. Since the method for setting logLevel varies by platform, please refer to the platform-specific guides below, set it to DEBUG level, and then proceed.

1. Verify logLevel setting: Confirm that logLevel is set to DEBUG when initializing the SDK.

2. Build and run the app: Build the app in Android Studio and install it on a test device.

3. Set Logcat filter:

   1. Open the Logcat tab at the bottom of Android Studio.

   2. Enter the package name of your client app in the filter field at the top right, then enter

      Airbridge to configure the system to display only Airbridge logs.

4. Reproduce the issue: Reproduce the situation where the problem occurs.

5. Save logs:

   1. Keep the app active for about 30 seconds.

   2. Select all logs in Logcat and copy them.

   3. Paste into a text editor (Notepad, VS Code, etc.) and save as a file.

You can directly collect logs using adb commands in the terminal. Platform Tools must be installed.

1. Clear Logcat buffer:

   adb logcat -c

2. Reproduce the issue: Reproduce the situation where the problem occurs.

3. Write to file:

   adb logcat "Airbridge:V" "*:S" > airbridge_logs.txt

   • After reproducing the issue, wait about 30 seconds, then stop saving logs.

4. Check the saved file: A file named airbridge_logs.txt will be created in the current directory.

1. Verify logLevel setting: Confirm that logLevel is set to DEBUG when initializing the SDK.

2. Connect device: Connect your iOS device to the Mac.

3. Build and run the app: Build the app in Xcode and install and run it on the connected device.

4. Set console filter:

   1. Open the Console tab at the bottom of Xcode.

   2. Enter Airbridge in the filter input field at the bottom right to display only Airbridge logs.

5. Reproduce the issue: Reproduce the situation where the problem occurs.

6. Save logs:

   1. Keep the app active for about 30 seconds.

   2. Select all logs in the Console and copy them.

   3. Paste into a text editor and save as a file.

If you cannot build directly to an iOS device with Xcode, you can collect logs using the Console app on Mac.

1. Connect device: Connect your iOS device to the Mac.

2. Open Console app: Search for "Console" in Spotlight (Cmd+Space) and launch the app.

3. Start log stream:

   1. Select the connected iOS device from the device selection menu next to the search bar at the top of the Console app.

   2. Enter the app's bundle ID in the search/filter field at the top to filter the results.

4. Clear logs: Right-click the Console window and select "Clear Console" to remove previous logs.

5. Reproduce the issue: Reproduce the situation where the problem occurs.

6. Save logs:

   1. Keep the app active for about 30 seconds.

   2. Select all displayed logs and copy them.

   3. Paste into a text editor and save as a file.

• Scope: Provide logs covering at least 30 seconds from issue reproduction to include the entire initialization, tracking, and processing flow.

• Filtering: It is recommended to filter to include only Airbridge-related logs.

• File format: Save and send in text file (.txt) format whenever possible.

  • SDK version

  • App installation method (standard installation, test distribution, etc.)

  • Device information (OS version, model name, etc.)

  • Time of occurrence (at a specific event, at app start, etc.)

  • Reproduction steps

• Environment information: Providing the following information will speed up problem analysis:

• DEBUG logs can expose sensitive internal operations. In release builds, they must be removed or restored to WARNING level or higher.