SUPApplicationCallback API

This callback protocol is invoked by events of interest to a mobile application.

You must register an SUPApplicationCallback implementation to your SUPApplication instance to receive these callbacks.

Callbacks in the SUPApplicationCallback Interface
Callback Description
- (void)onApplicationSettingsChanged :(SUPStringList*)names Invoked when one or more application settings have been changed by the server administration.
- (void)onConnectionStatusChanged :(SUPInt)connectionStatus :(SUPInt)errorCode :(SUPNullableString)errorMessage Invoked when the connection status changes. The possible connection status values are defined in the ConnectionStatus class.
- (void)onDeviceConditionChanged :(SUPInt)deviceCondition Invoked when a condition is detected on the mobile device that may be of interest to the application or the application user. The possible device condition values are defined in the SUPDeviceCondition class.
- (void)onRegistrationStatusChanged :(SUPInt)registrationStatus :(SUPInt)errorCode :(SUPNullableString)errorMessage Invoked when the registration status changes. The possible registration status values are defined in the SUPRegistrationStatus class.
- (void)onHttpCommunicationError :(int32_t)errorCode :(NSString*) errorMessage :(SUPStringProperties*)responseHeaders; Invoked when an HTTP communication server rejects HTTP communication with an error code.
  • errorCode – Error code returned by the HTTP server. For example: code 401 for authentication failure, code 403 for authorization failure.
  • errorMessage – Error message returned by the HTTP server.
  • responseHeaders – Response headers returned by the HTTP server.