Troubleshooting

Quick fixes for the most common integration issues. Can't find your issue here? Enable debug logging first — it usually points straight to the cause.

Symptom	Likely cause	Fix
Notifications aren't delivered at all	Environment mismatch — app is built against dev but Actito is sending to prod (or vice versa), or FCM credentials don't match the environment	Check your Actito app to confirm the Push service config and your app's actito-services.json point to the same environment, keys, and Firebase credentials. See Notification Provider Environments
SDK behaves inconsistently after manually editing app data	The SDK's shared preferences were modified or deleted directly	Never edit SDK-managed shared preferences by hand. Use disableRemoteNotifications() to stop notifications, or unlaunch() to fully reset the SDK
Not enough detail in logs to diagnose an issue	Default logging level is too low	Enable debug logging (see below)

Enabling debug logging

Add this to your AndroidManifest.xml:

<?xml version="1.0" encoding="utf-8"?>
<manifest>
    <application>
        <meta-data
            android:name="com.actito.debug_logging_enabled"
            android:value="true" />
    </application>
</manifest>

This enables verbose logging, so you can trace initialization and runtime behavior across SDK modules.