10. The built-in Configuration Dashboard / Test Suite

AKS bundles a Compose-based diagnostics screen — there's no separate debug build or manifest entry for it; it renders as a full-screen dialog on top of whatever Activity you launch it from. It's useful for checking what AKS thinks is going on (remote config, ad states, consent) without attaching a debugger.

Opening it

Call this from anywhere you have an Activity reference — a hidden row in your own settings screen, a long-press on your app's version number, a debug-only button, whatever trigger you wire up (AKS doesn't add a trigger for you):

AppsKitSDK.showGodModeScreen(PlatformActivity(this))

This opens the AKS Configuration Dashboard, from which you can check:

• Enable Ads — a toggle, and GDPR Status — a read-only TRUE/FALSE reflecting AdsManager.isUserConsentsProvided().
• Check Configurations — opens the Test Suite itself (see below).
• Placeholder Calls — a pretty-printed JSON dump of ad call activity per placeholder.
• Placeholder Load Stats — load attempt/success/failure counters per placeholder.
• AKS Logs — the same accumulated log history you'd otherwise read from Logcat (see §11), searchable on-screen.

The Test Suite

Tapping Check Configurations opens the Test Suite screen, showing: test mode / dev mode flags, whether the default (offline) config or the fetched remote config is currently active, the AKS SDK version, the raw remote-config JSON AKS fetched, and live state + last-shown time for Interstitial, Rewarded, and App Open, plus the current session count and day count.

You can also jump straight there without going through the dashboard:

AppsKitSDK.showAKSTestSuit(PlatformActivity(activity))

Both calls only need a PlatformActivity — AKS reads everything else (ad states, config, session data) internally.