Notifications to Huawei devices (HMS Push Kit)
Huawei devices without Google Play Services cannot receive Firebase (FCM) notifications. Pushizo sends to these devices through Huawei Push Kit with the hms_push channel…
Huawei devices without Google Play Services cannot receive Firebase (FCM) notifications. Pushizo sends to these devices through Huawei
Push Kit with the hms_push channel (docs/adr/0025-hms-flutter-web-catalyst-konum.md).
1. AppGallery Connect
- AppGallery Connect → My projects → select your app → Grow → Push Kit → Enable.
- Project settings → General information: copy the App ID (numeric) and Client secret values.
- From the same page, download the
agconnect-services.jsonfile, place it in your Android app'sapp/folder and add the SHA-256 signing certificate fingerprint.
2. Dashboard
Apps → Channels → Huawei Push (HMS): enter the App ID and Client Secret, then click Save and validate. Pushizo obtains an OAuth
token and verifies the credentials by making a validate_only send to a fake device. The Client Secret is stored
encrypted and never shown again; if you leave it empty when updating, the saved value is kept.
Enable High-priority data messages only if you have obtained high-priority permission from Huawei; when it is off, messages are sent with normal priority (they may be delayed if the device is in sleep mode).
With the API:
curl -X PUT https://api.pushizo.com/internal/v1/apps/$APP_ID/channels/hms_push \
-H "Content-Type: application/json" -b cookies.txt \
-d '{"provider":"hms","app_id":"104123456","client_secret":"<client-secret>"}'3. Android SDK
Add the pushizo-hms module; details in Android SDK → Huawei (HMS). In an app with the module added,
if the device has no Google Play Services but has HMS Core, the SDK automatically registers an hms_push subscription;
other devices use FCM. A device has a single push subscription.
Sending
In campaign, automation and API sends, the push channels (ios_push, android_push, hms_push, web_push) are targeted
together; the content is the same as Android (title, text, image, buttons, notification channel, URL). To send only to Huawei
devices, use target.channels: ["hms_push"].
Troubleshooting
| Symptom | Cause |
|---|---|
Channel invalid, OAUTH_FAILED | Wrong App ID or Client Secret; it may have been confused with the "App secret". |
80300002 | Push Kit is not enabled for this app, or the signing fingerprint is missing. |
Delivery failed (80300007) | Device token is invalid (app uninstalled); the subscription is marked invalid. |
| Notifications are delayed | No high-priority permission; messages are sent with normal priority. |
Android Push (FCM)
The Firebase Cloud Messaging HTTP v1 channel — service account, data-only message model, Android content fields, notification channels, delivery feedback and troubleshooting.
Android delivery hardening
On some Android manufacturers notifications arrive late or not at all. This guide explains why, how Pushizo measures it, and how to take users to the right settings screen in your app.