Skip to main content
SDK Version

Troubleshooting

This article covers the most common issues encountered when integrating and using the Actito SDK. Each section provides guidance to help you quickly identify and resolve configuration or runtime problems.

Enabling debug logging​

There are times when the default logging level is not sufficient to diagnose problems. You can enable debug logging by adding the following to the AndroidManifest.xml.

<?xml version="1.0" encoding="utf-8"?>
<manifest>

    <application>

        <meta-data
            android:name="re.notifica.debug_logging_enabled"
            android:value="true" />

    </application>

</manifest>

Problem sending notifications​

If notifications are not being delivered as expected, the most common cause is an environment mismatch. This typically occurs when the application is targeting the wrong environment (for example, sending from production to a development build) or when incorrect FCM credentials are configured for that environment.

You can verify in your [Actito app] that your Push service configurations and your application’s configuration are aligned in terms of environment, application keys, and Firebase credentials.

You can also check the documentation on Notification Provider Environments for more information on environment configuration.

Managing application state​

The Actito SDK stores essential application data — such as the current device information, registration details, and push notification state — in the system’s shared preferences.

It is important not to manually delete or modify these files or properties. Doing so may lead to inconsistent behavior, including partial resets or desynchronization with Actito.

If you need to clear or reset specific aspects of the SDK’s state, always use the appropriate public APIs that safely handle cleanup operations. For example:

  • Use disableRemoteNotifications() to stop receiving push notifications.
  • Use unlaunch() to fully unregister the SDK and remove all device-related data.

These methods ensure that both local and remote data remain consistent and that the SDK continues to operate as expected.