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​

In some cases, the default logging level may not provide enough detail to diagnose an issue. You can enable more granular logs by adjusting the SDK’s log level using the setLogLevel() function.

import { setLogLevel } from 'actito-web/core';

setLogLevel('debug');

This enables verbose logging, allowing you to better trace initialization and runtime behavior across SDK modules.

HTTP 403​

If you encounter HTTP 403 (Forbidden) errors when the SDK attempts to communicate with the Actito APIs, it usually indicates that your domain has not been authorized to use the Actito SDK.

To resolve this issue, your website’s domain must be explicitly added to the list of Allowed Domains associated with your application configuration.

Action required

You can add your domain in the Allowed Domains list in your Actito app. Once your domain is authorized, the SDK will be able to perform network requests successfully.

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 local storage.

It is important not to manually delete or modify these 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.

Google Maps Key​

The Actito Push UI module requires access to the Google Maps API when rendering notifications containing map content. A common issue is neglecting to obtain or configure the required Google Maps API Key.

Ensure you have properly generated and enabled a Google Maps Key for your project. You can find detailed setup instructions in the Setting Up Google Maps Guide.

Website Push in Safari​

When configuring Website Push notifications for Safari, one common issue arises from using icons that contain transparency (alpha channels). Although these icons are accepted during upload, they will cause delivery errors, preventing notifications from being sent.

To avoid this issue, always ensure that your Safari push icon is a fully opaque image (no transparency).

Important

If you change the Safari push icon after users have already subscribed to notifications, they must unsubscribe and re-subscribe in order for the new icon to take effect. Keep this in mind when updating assets in production environments to ensure consistent notification delivery.