|A subscribe event experienced connection issues when running.|
|SDK was able to reconnect to pubnub.|
|SDK subscribed with a new mix of channels (fired every time the |
channel group mix changed).
|Used API reported success with this status category.|
|Request failed because of access error (active PAM). |
status.AffectedChannelGroups contain list of channels and/or groups to which user with specified
auth key doesn't have access.
|Used API didn't receive a response from server in time.|
|Client unsubscribed from specified real-time data channels.|
|Subscribe loop failed and at this moment client is disconnected from real-time data channels. This could due to the machine or device is not connected to Internet or this has been lost, your ISP (Internet Service Provider) is having to troubles or perhaps or the SDK is behind of a proxy.|
|Request cannot be completed as not all required values have been passed (like |
publish key) or passed values are of unexpected data type.
|Subscription request cannot be processed as the passed filter expression is malformed and cannot be evaluated.|
|Request received in response non-JSON data. It can be because of an error message from the proxy server (if applicable).|
|History API may return this status category in case if some messages can't be decrypted.|
|TLS handshake issues. In most cases is because of poor network quality and packets loss and delays.|
|This status event will be fired each time the client receives more messages than the value of RequestMessageCountThreshold, set in |
In case of network disconnect the PubNub client SDK will attempt to reconnect a finite number of times after which this status is sent and the re-connection attempts will stop.
|PubNub SDK returns this error for SDK exceptions or when server responds with an error.|