Unable to Create Push Subscription – “Client identification sequence is not valid” (422 Error)

[Kumar-Evoke-Github]

Hello QuickBlox Support Team,

We are facing an issue while trying to create a push subscription in our Android app using QuickBlox SDK. The API is returning the following error:

STATUS CODE: 422
BODY: {"errors":{"base":["Client identification sequence is not valid."]}}

Endpoint:
POST https://api.quickblox.com/subscriptions.json

Headers:

QuickBlox-REST-API-Version: 0.1.1
QB-SDK: Android 4.3.3
QB-Token: eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9...
Content-Type: application/x-www-form-urlencoded; charset=UTF-8

Parameters:

notification_channels=gcm
push_token[client_identification_sequence]=cuaKtcO5TWGbXGBYsFIxOn:APA91bEmUrNUwPHm3xiCrxdKeIdaBTz6twPAqYLDf6w1E59wqEMLPO8Om-7BUkvFB1mezdaHNFa6WuerDCbMNrKSnf_DqU5F301U0eyVNReKhDoeIJgXVw0
device[udid]=139217073_ffffffff-c07b-44d8-0001-9f8b79428ae9
device[platform]=android
push_token[environment]=production

Response

Status: 422 Unprocessable Entity
Headers:

Content-Type: application/json; charset=utf-8
QuickBlox-REST-API-Version: 0.1.1
QB-Token-ExpirationDate: 2025-09-03 12:43:26 UTC
Server: QuickBlox
Date: Wed, 03 Sep 2025 10:43:26 GMT

Body:

{
"errors": {
"base": [
"Client identification sequence is not valid."
]
}
}

Request Details:

Endpoint: POST https://api.quickblox.com/subscriptions.json

QB SDK Version: Android 4.3.3

App ID: [Your QuickBlox App ID]

Environment: [Development / Production]

QB-Token: [Valid session token is being passed]

Device Udid: [e.g., 139217073_ffffffff-c07b-44d8-0001-9f8b79428ae9]

FCM Token (registrationID): [Example token string from FirebaseMessaging.getInstance().token]

What we have verified:

We are using a valid FCM token (long alphanumeric string from Firebase).

Firebase is initialized correctly with google-services.json.

App is logged in to QuickBlox before attempting subscription.

Correct environment (DEVELOPMENT / PRODUCTION) is being passed.

Despite this, subscription fails with the same error.

Expected Behavior:
Push subscription should be created successfully with the provided FCM token, and a subscription_id should be returned.

Actual Behavior:
API responds with 422 – Client identification sequence is not valid.

Could you please check on your side if this is an issue with:

FCM token validation in QuickBlox API, or

Any additional configuration required in QuickBlox dashboard for our app?

Please advise on the next steps.

[mohitquickblox]

Hello @Kumar-Evoke-Github , Can you please share your registered email address associated with the QuickBlox account?
Kindly also specify some example ids of push notification fails, if available.

You may use my email address mohit@quickblox.com for communicating.

[Kumar-Evoke-Github]

Hi Mohit,
We are currently using the account subscriptions@starchase.com.

Note: You can run the sample project "chat-kotlin" from GitHub and observe the same issues. It is not creating subscriptions by default, and even when done manually, it is not working with version 2.3.3.

[mohitquickblox]

Hello @Kumar-Evoke-Github ,

Can you please verify the following:

1. The “package_name” in google_services.json file must be same as the “applicationId” in the application’s gradle file. If this is not the case, you must change the application id in the project to match with the google_services.json file.

2. You must generate and upload the correct service account key on their QB admin dashboard. You may follow this guide: https://docs.quickblox.com/sdks/android-push-notifications#1-generate-a-new-service-account-key

3. All the steps according to our documentation must be followed: https://docs.quickblox.com/sdks/android-push-notifications#configure-firebase-project-and-api-key

Please do let us know your feedback after verification of these 3 steps.

[Kumar-Evoke-Github]

Hi Mohit,

I have checked and confirmed that the package name is the same in both json and gradle. While running the app, I noticed the following in the logs:

✅ Account settings: 200 OK

✅ Session creation: 201 Created

✅ Login: 202 Accepted

✅ User fetch: 200 OK

❌ Subscriptions API: multiple failures (422 Unprocessable Entity, and once 404 Not Found)

This indicates that session and login flows are working fine, but the issue is specifically with the subscriptions.json request. It seems the app is unable to create subscriptions successfully, which might be affecting push notifications and call functionality.

https://api.quickblox.com/account_settings.json (responseCode: 200, responseTime: 1773.956ms)
https://browser-intake-datadoghq.com/api/v2/logs (responseCode: 202, responseTime: 1885.355ms)
https://api.quickblox.com/session.json (responseCode: 201, responseTime: 905.148ms)
https://api.quickblox.com/login.json (responseCode: 202, responseTime: 816.369ms)
https://api.quickblox.com/session.json (responseCode: 201, responseTime: 963.447ms)
https://api.quickblox.com/users/139217073.json (responseCode: 200, responseTime: 963.469ms)
https://api.quickblox.com/subscriptions.json (responseCode: 422, responseTime: 961.639ms)
https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/batchlog
https://api.quickblox.com/subscriptions.json (responseCode: 404, responseTime: 1610.282ms)
https://api.quickblox.com/subscriptions.json (responseCode: 422, responseTime: 943.867ms)
https://api.quickblox.com/subscriptions.json (responseCode: 422, responseTime: 947.365ms)
https://api.quickblox.com/subscriptions.json (responseCode: 422, responseTime: 938.673ms)
https://api.quickblox.com/subscriptions.json (responseCode: 422, responseTime: 903.049ms)

One more observation:

The subscriptions.json endpoint is being called repeatedly in a loop.

The same code was working fine with QuickBlox SDK 4.1.3, but the issue started after upgrading to 4.3.3.

Could you please help review why this behavior is happening in 4.3.3 and what needs to be corrected for the subscriptions API?

[mohitquickblox]

Hello @Kumar-Evoke-Github, We were able to complete a round of testing on our SDK version 4.3.3. Unfortunately, we did not encounter any issues in subscription creation.

Please see the logs here:

QB Logs.txt

To investigate your issue further, we need further information from your end. Please provide:

1. Googleservices.json file
2. Application id
3. serviceaccountkey.json file

You may share them to my email id as well: mohit@quickblox.com