Using the Debug and test features
The SDK gives developers the option of enabling a debugging gesture when running the application by enabling this as part of theCIMobileAdsConfiguration, since version 1.2.0, the debug gesture is enabled by default.
When enabled and the user performs the gesture. This will open a debug menu, which gives the following options:
Clear ads configs cache
When updating configs in the Fusion platform, these are stored by the SDK and refreshed periodically. Pressing this button will force the SDK to download the new configs from the server.Clear floors cache
When updating floors data within fusion, this data is stored by the SDK and refreshed periodically. Pressing this button will force the SDK to download the new floors data from the server.Start a new debug session
Opens a dialog where the user is required to enter a PIN which is provided within the Fusion dashboard. When this PIN is entered correctly, the SDK will start sending detailed logs for a fixed period of time to the Content Ignite team to allow them to diagnose issues more effectively.Enabling / Disabling Test ads
During development to prevent invalid traffic in Google Ad Manager, we recommend you enable test ads. This guarantees an ad will always be served, either from GAM or Prebid depending on your setup, helping for use during demos.Using the Debug overlay (Compose only)
As a shortcut to the gesture based access to the debug menu, you also have the option of using theCIDebugOverlay during development, which opens up the debug menu, simply add the CIDebugOverlay to your Compose UI. See the demo app. This feature will be added to the View-Based API in a future version.