This enumeration defines the error codes that may be returned as a result of a Push Service operation.
#include <bbpush/push_errno.h>
enum PushErrorCode{
PUSH_NO_ERR = 0
PUSH_ERR_INTERNAL_ERROR = 500
PUSH_ERR_CONNECTION_CLOSE = 501
PUSH_ERR_NO_PERM_CREATE_CONNECTION = 502
PUSH_ERR_INVALID_PIN = 10001
PUSH_ERR_INVALID_PROVIDER_ID = 10002
PUSH_ERR_USER_ALREADY_UNREGISTERED = 10004
PUSH_ERR_ALREADY_UNSUBSCRIBED_BY_PROVIDER = 10005
PUSH_ERR_INVALID_SUBSCRIPTION_STATUS = 10006
PUSH_ERR_PIN_NOT_FOUND = 10007
PUSH_ERR_SUBSCRIPTION_REQUEST_TIME_OUT = 10008
PUSH_ERR_INVALID_ACCESS = 10009
PUSH_ERR_SUBSCRIPTION_LIMIT_EXCEEDED = 10010
PUSH_ERR_INVALID_SUBSCRIPTION_PARAMETERS = 10011
PUSH_ERR_SUBSCRIPTION_ALREADY_SUSPENDED_BY_PROVIDER = 10012
PUSH_ERR_SESSION_NOT_FOUND = 10100
PUSH_ERR_PPGURL_MISSING = 10102
PUSH_ERR_TRANSPORT_FAILURE = 10103
PUSH_ERR_INVALID_COMMAND = 10104
PUSH_ERR_COMMAND_NOT_SUPPORTED = 10105
PUSH_ERR_USER_NOT_REGISTERED = 10106
PUSH_ERR_SUBSCRIBE_MISSING_PORT = 10107
PUSH_ERR_SUBSCRIBE_MISSING_RC = 10108
PUSH_ERR_PPG_SERVER_ERROR = 10110
PUSH_ERR_INVALID_TARGET_KEY = 10111
PUSH_ERR_SESSION_ALREADY_EXISTS = 10112
PUSH_ERR_INVALID_PPG_URL = 10114
};
BlackBerry 10.2.0
Operations this error can occur on: Create Session, Create Channel, Destroy Channel, Register to Launch, Unregister from Launch.
Recommended action: Retrying the operation might correct the issue.
Since: BlackBerry 10.2.0
Operation this error can occur on: Create Session, Create Channel, Destroy Channel, Register to Launch, Unregister from Launch.
Recommended action: This error will trigger the #push_connection_close_callback callback where the application or service needs to re-establish the connection with the PNS Agent. Retry the operation once the connection has been re-established. See push_service_set_connection_close_callback().
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Session, Create Channel, Destroy Channel, Register to Launch, Unregister from Launch.
Recommended action: If you are writing a consumer application for the general public, make sure you specify the following permission tag in your bar-descriptor.xml file:
<permission system="true">_sys_use_consumer_push</permission>
If you are writing an enterprise application, make sure your application is installed in the Work perimeter.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Retrying the operation might not be helpful since this is most likely an unrecoverable error that is out of control of the application. It might make sense to communicate this issue up to the user.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Session, Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Fixing the application ID programmatically and retrying might correct the issue. The provider application ID is set by calling the push_service_set_provider_application_id() API.
Since: BlackBerry 10.2.0
Operations this error can occur on: Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Most applications will typically want to just ignore this error code when it comes back.
Since: BlackBerry 10.2.0
Operations this error can occur on: Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Most applications will typically want to just ignore this error code when it comes back.
Since: BlackBerry 10.2.0
It would only occur if a create or destroy channel operation internally causes the state of a subscriber on the PPG to be in an invalid state.
Operations this error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: If this error occurs, it should be logged and reported to the RIM support team.
Since: BlackBerry 10.2.0
Operations this error can occur on: Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: This error can most likely be ignored since if the subscriber could not be found on the PPG's end, then destroying the channel will have no effect anyway (it is as if they were never registered with the PPG using create channel).
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Retrying the operation might correct the issue.
Since: BlackBerry 10.2.0
It would only occur if a create channel or destroy channel operation internally passes an invalid authentication token to the PPG.
Operations this error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: If this error occurs, it should be logged and reported to the RIM support team.
Since: BlackBerry 10.2.0
The create channel is described as still "active" because no destroy channel has been done for it.
Operations this error can occur on: Create Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: No action can be taken by the application for this error, but it should somehow be communicated back to the content provider and then to RIM to try to increase the allowed subscription limit.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Retrying the operation is not recommended since this is an unrecoverable error that is out of control of the application. It might make sense to communicate this issue up to the user.
Since: BlackBerry 10.2.0
Similar to the PUSH_ERR_ALREADY_UNSUBSCRIBED_BY_PROVIDER error.
Operations this error can occur on: Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Most applications will typically want to just ignore this error code when it comes back.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel, Destroy Channel, Register to Launch, Unregister from Launch.
Recommended action: This usually means a programming error in the application.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel.
Recommended action: This usually means a programming error in the application. Make sure that a PPG URL is specified when performing a Create Channel operation.
Since: BlackBerry 10.2.0
Operation: This error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: After receiving the push_transport_ready_callback_t callback, retry the operation. This error can also occur when the user's wireless connection (e.g., Wi-Fi, Mobile Network) is off or temporarily down, so it might make sense to communicate this issue to the user.
Since: BlackBerry 10.2.0
Operations this error can occur on: custom write operation to the Push Service file descriptor.
Recommended action: This usually means a programming error in the application. Instead of writing to the Push Service file descriptor directly, it is recommended to use the push_service_t structure.
Since: BlackBerry 10.2.0
Recommended action: This operation/feature might not yet be implemented and so should not be performed.
Since: BlackBerry 10.2.0
Operations this error can occur on: Destroy Channel.
Recommended action: This might mean a programming error in the application.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel.
Recommended action: Retrying the operation might correct the issue.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Retrying the operation might correct the issue.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: After receiving the push_transport_ready_callback_t callback, retry the operation.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Session.
Recommended action: Fixing the invocation target key programmatically and retrying might correct the issue. The invocation target key is set by calling the push_service_set_target_key() API.
Since: BlackBerry 10.2.0
This result code can occur from any of the following operations: Create Session.
Recommended action: Check the application provider ID and target key to ensure that they are valid and unique.
Since: BlackBerry 10.2.0
Operations this error can occur on: Create Channel, Destroy Channel (only if using the BlackBerry Internet Service as the PPG).
Recommended action: Check that the PPG URL is valid.
Since: BlackBerry 10.2.0