> ## Documentation Index
> Fetch the complete documentation index at: https://docs.contentignite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Debug features

> Using the Debugging features

## 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 the `CIMobileAdsConfiguration`, since version 1.2.0, the debug gesture is enabled by default.

![Debug Gesture](https://gitlab.com/content-ignite/cimobilesdk-android/-/raw/main/debug-gesture.gif)

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](https://www.contentignite.com/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.

This can also be controlled using the `testAds: Boolean` parameter on `ContentIgniteSDK.initialise`.