DebugMode enables you to see the event data logged by your app in near real-time. This is very useful for validation purposes during the instrumentation phase of development and can help you discover errors and mistakes in your Analytics implementation and confirm that all events and user properties are logged correctly.

In DebugMode events saved to local storage are pushed to REST API every 10 seconds and are stored in offline mode up to 1 hour.

Additionally, in DebugMode you will get all the logging printed in Logcat.

2.7.0 and onwards

To enable debug mode during configuration use setDebug method

Reteno.initWithConfig(
    RetenoConfig.Builder()
        .accessKey("your_access_key_here")
        .setDebug(true)
        .build()
)

📘
Note
Use debug mode only with test devices or developer accounts

Before 2.7.0

To enable DebugMode run the following command in CLI (no app recompilation is required):

adb shell setprop debug.com.reteno.debug.view enable

To disable DebugMode run the following command in CLI:

adb shell setprop debug.com.reteno.debug.view disable

Troubleshooting Steps:

The notification service is not configured: Configure FCM.
Push tokens/device data are absent: Check that you have allowed notifications on the device and configured the token transfer. Details >
TheDelivered message statuses are absent: Check your message delivery data settings. Details >
TheClicked message statuses are absent: Click the notification, or check click tracking in the code. Details >
User profile updates are absent: Ensure you send user data when you identify them. For example, when they sign in to the app. Details >

More on debugging in eSputnik account >