11. Debugging with AKS logs (PTB_LOG)

Every log line AKS produces — from AKSLogManager/AppsKitSDKLogManager calls, ad load/show events, and internal SDK activity — goes to two places at once: Logcat, tagged by category, and the in-memory log accumulator that backs the AKS Logs screen in §10.

Filtering Logcat

Filter by tag in Android Studio's Logcat (tag:PTB_LOG) or via adb:

adb logcat -s PTB_LOG:* PTB_LOG_ADS:* PTB_LOG_ANALYTICS:*

• PTB_LOG — general SDK logs (init sequence, mode banners, lifecycle, errors)
• PTB_LOG_ADS — ad load/show lifecycle for every format
• PTB_LOG_ANALYTICS — events sent to Firebase/MMPs, including every sendAKSEvent/AKSLogManager.log call from §7

Reading logs without Logcat

If you're debugging a release build, a tester's device, or a support ticket where attaching adb isn't an option, open the Test Suite's AKS Logs screen instead (§10) — it shows the exact same log lines on-device, with on-screen search, so a tester can scroll/search it directly or screenshot it back to you.

AppsKitSDKLogManager.logAarVersion() (see §7.3) is the fastest way to confirm which AKS AAR version is actually integrated when you suspect a version mismatch — it prints the version banner to PTB_LOG.