Error handling
This page outlines the errors associated with the TIXNGO SDK.
The Fan App is required to listen for the SDK's onErrorHandler() callback and provide relevant messages or actions to the user, depending on the type of error encountered.
Errors generated by the TIXNGO SDK are encapsulated within the “TixngoSDKError” structure, which includes three properties:
code: An integer (not nullable)
message: A string (nullable) that provides further explanation regarding the error code
userInfor: A dictionary (nullable) containing detailed error information in raw data format
Code | Message | UserInfor | Description |
|---|---|---|---|
9998 | dynamic | null | This exception is thrown when TIXNGO SDK encounters an internal error. |
9999 | “Have an exception error from SDK” | null | This exception is thrown when TIXNGO SDK encounters an internal error. Cannot parse error data. |
10000 | “You must initialized to access this feature.” | null | This exception is thrown when TIXNGO SDK in initializing process and the host app try to access. |
10001 | “You must log in to access this feature.” | null | deprecated |
403 | MAX_NUMBER_SECURITY_TOKEN |
| This exception is thrown when the user reach max active session.. |
403 | TOO_MANY_REGISTERED_DE |
| This exception is thrown when the user reach max registered devices for the account. |
403 | NO_TICKET_ELIGIBILITY |
| This exception is thrown when TIXNGO SDK encounters current account don’t have at least one ticket. |
409 | CONCURRENCY_UPDATE_CONFLICT |
| This exception is thrown when TIXNGO SDK encounters an error from the backend with a concurrency issue. |
423 | LOCKED |
| This exception is thrown when the TIXNGO switch frozen mode for disaster recovery. |
|
|
|
|
© TIXNGO 2023 - Login