Step 4. Send remote push notifications
The app client SDK does not send Android remote push (FCM) messages directly. The Hive Axyl push server receives send requests and delivers the messages to FCM, and the app client registers its device token so that it can be a send target and handles the messages that arrive.
Client SDK coverage
The current SDK surface of IPushService provides device token registration, token language change, notification consent change, and token identifier unbinding. Methods that send remote push messages are not included in the client SDK.
| Category | Supported | Description |
|---|---|---|
| Device token registration | Supported | UpsertTokenAsync() |
| Token language change | Supported | PatchTokenLanguageAsync() |
| Notification consent change | Supported | PatchTokenAgreementAsync() |
| Token identifier detachment | Supported | DetachTokenIdentifierAsync() |
| Remote push sending | Not supported | Performed in the Hive Console or through the server API |
`
Send from the server
Include the target users, App ID, message body, per-language messages, and Android notification options needed for the send request in the server API request body. For detailed field definitions, see Send remote push notifications (Server API).
The app client does not call a send method. So that the server can send pushes, register the FCM token with the Hive Axyl push server after login.
Next steps
Implement Step 5. Receive remote push notifications.