Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Made minor changes

...

Multiexcerpt
MultiExcerptNameerror

If you receive a message similar to "Error enabling Cloud service for the project" in Studio when trying to enable Cloud services for your project, the Mobile Backend Services (MBS) server may be down or Studio is unable to connect to the MBS server. Try to enable Cloud services later.


If you are still receiving this error when trying to enable Cloud services, check to see if your application was created in https://platform.appcelerator.com/.

...

CodeMessageDescription
3001Too many messages were sent to a specific device. Retry sending after a while.FCM limits the number of push messages that can be sent to a particular device over a period. Increase the period between notifications for this device.
3002A particular message could not be sent because the FCM servers encountered an error.FCM servers encountered an error.
3003Bad registration_id. Sender The sender should remove this registration_id.The FCM client sent a bad registration ID and should re-register with FCM to obtain a new ID. This error is uncommon if you are using the Modules.CloudPush module.
3004Time-to-live value provided is less than zero, or more than the allowed maximum.The message's Time to Live (expiration date) value is invalid. This error is uncommon if you are using the Modules.CloudPush module.
3005Payload is longer than the maximum allowed size of 4096 bytes.FCM limits push notification payload size to 4096 bytes; try reducing the JSON message size and sending again.
3006The sender_id contained in the registration_id does not match the sender_id used to register with the FCM servers.The FCM client did not use the proper sender_id. This error is uncommon if you are using the Modules.CloudPush module.
3007Collapse key is required. Include collapse key in the request.If you are using a custom FCM client you need to include a collapse key in the request. This error is uncommon if you are using the Modules.CloudPush module.
3008The request was missing a registration_id; registration_id is required with every request. The FCM client did not include a registration ID in its request. This error is uncommon if you are using the Modules.CloudPush module.
3009The user has uninstalled the application or turned off notifications. Sender The sender should stop sending messages to this device and delete the registration_id. The client needs to re-register with the FCM servers to receive notifications again. 
3010Too many messages sent by the sender. Retry after a while.FCM limits the number of push notifications that can be sent by a particular sender over a given period. Increase the period between push notification send requests.
3011A particular message could not be sent because the FCM servers were not available.The FCM server was not available for an unknown reason. Try again later.
3101No result retrieved from FCM Server.The FCM server did not return a response from the push notification request.
3102fcm_apiKey is null.Make sure you've configured Mobile Backend Services push notifications with your API key.
3103RegistrationId(s) is null or empty.The FCM client provided a null or empty registration ID. This error is uncommon if you are using the Modules.CloudPush module.
3104FCM internal error.An internal error occurred with FCM. Check FCM status.
3105Message could not be sent, or there was a JSON parsing error.Make sure that the notification JSON payload is properly formatted.