-
Notifications
You must be signed in to change notification settings - Fork 688
Description
Hello QuickBlox Support Team,
We’re unable to create a push subscription on Android; this blocks incoming audio/video calls from ringing when the app is in background or terminated state.
Key note: We tested both your public Sample Android Chat project (from GitHub) and our own application — neither creates a subscription.
Error (from both apps)
POST https://api.quickblox.com/subscriptions.json
Status: 422 Unprocessable Entity
Body: {"errors":{"base":["Client identification sequence is not valid."]}}
Recent request/response example (from our app):
Request
Endpoint: POST https://api.quickblox.com/subscriptions.json
Headers:
QuickBlox-REST-API-Version: 0.1.1
QB-SDK: Android 4.3.3
QB-Token:
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Params:
notification_channels=gcm
push_token[client_identification_sequence]=<FCM registration token from FirebaseMessaging.getInstance().token>
device[udid]=139217073_ffffffff-c07b-44d8-0001-9f8b79428ae9
device[platform]=android
push_token[environment]=production
Response
Status: 422
Body:
{"errors":{"base":["Client identification sequence is not valid."]}}
(We can attach full raw logs if helpful.)
What we’ve verified
FCM token used is the actual registration token (long string from FirebaseMessaging.getInstance().token), not Sender ID/App ID.
Firebase configured correctly with google-services.json; package name matches applicationId.
User is logged in (valid QB-Token present) before subscription call.
Environment matches (we tried both DEVELOPMENT and PRODUCTION).
Reproduces on QuickBlox sample app and our app (multiple devices).
Impact / Request
We need QuickBlox push subscriptions working so that WebRTC audio/video calls will ring and wake the app in background and terminated states (high-priority FCM data push).
Please help identify why FCM tokens are being rejected with “Client identification sequence is not valid.”
Questions / Things to check on your side
Is there any server-side configuration required on our QuickBlox app (e.g., Firebase Server Key (Legacy) / FCM credentials) that could cause this error if missing or mismatched?
Does the Android SDK 4.3.3 require any specific FCM mode (Legacy HTTP vs HTTP v1) or payload format for subscriptions?
Any known issues recently affecting /subscriptions.json validation for Android?
App details
QuickBlox App ID: [your-app-id]
QB SDK: Android 4.3.3
Android versions / devices tested: [list a few]
Package name(s): [com.your.app] (and the sample app’s)
Happy to provide:
Full request/response logs (headers & bodies, redacted as needed)
AndroidManifest.xml push meta-data section
Firebase project identifiers (redacted)
Test FCM tokens (redacted)
Thanks in advance for your help—this is currently blocking background/terminated A/V call reliability for our release.