Skip to main content

Associate your user

Call login after your own authentication succeeds and Pushctl registration is confirmed. Use a stable, non-secret ID from your backend. The callback runs after the API accepts the association.
Call logout when that user signs out:
The installation stays subscribed anonymously after a successful logout. Login and logout report an error when the installation is not registered or the API update fails.

Handle notification interaction

Remove a retained listener when its owner is destroyed:

Delivery analytics

The SDK persists events before sending and retries them during later starts, registrations, and events. Deterministic event IDs make these retries safe.
Notification data values are strings. Use an application-level schema and parse them defensively.