Troubleshooting
Appnext Android SDK 2.0 supports a debug mode that enables verbose SDK logging for local development and QA, making it easier to verify integration and ad lifecycle events without attaching a debugger.
Step 1. Enable Debug Mode
Enable Debug Mode:
AppnextSDK.getInstance().initialize(context)
AppnextSDK.getInstance().setDebugMode(context, true)
Important: Debug mode only activates in debuggable builds. The SDK checks whether the host app itself is debuggable (android:debuggable) and combines that with the flag you pass in. Passing true in a release-signed build has no effect.
Step 2. View Debug Logs
Once enabled, the SDK prints a diagnostic banner to Logcat under the tag AppnextSDK-Inspector, containing the SDK version, package name, Android API level, and current WebView version:
adb logcat -s AppnextSDK-Inspector
Available Method
- setDebugMode - Boolean. Enables or disables verbose SDK logging. Takes effect only when combined with an android:debuggable build (enabled = debug && appIsDebuggable).
Need Help?
If you need additional help with your Appnext SDK integration, contact our integration support team at [email protected].
Updated about 6 hours ago
