All Products
Search
Document Center

Mobile Platform as a Service:Gateway result code description

Last Updated:May 15, 2023

This topic describes the result codes that appear when you use a mobile gateway.

Result code on the gateway side

  • 1000 indicates that the API call is successful, while others indicate failure.

  • 1001-5999 and 7XXX indicate gateway errors.

    • 7XXX indicates that the wireless bodyguard reports an error during signature verification or decryption. For more information, see Wireless bodyguard result code description.

    • In addition to the result code, you can view the Memo and tips fields in the response header for more error information.

    • Public cloud users can also view detailed error information through the ~/logs/gateway/gateway-error.log logs on the gateway server.

  • If an exception occurs, you can try to troubleshoot the error by using the gateway exception troubleshooting. For more information, see Troubleshoot gateway exceptions.

Response code

Description

Explanation

1000

Processing succeeded

The gateway API call is successfully processed.

1001

Access is denied.

The Mock format is invalid, the resultStatus is missing, WAF verification fails, or the user of the authentication interface is not authorized to access.

1002

The number of calls exceeds the limit.

This exception occurs when traffic limit is triggered after you turn on Traffic limit configuration.

1005

No permissions

After you enable API authorization, the authorization verification fails when you call the API.

2000

Your logon session has timed out.

If the authorization verification feature is enabled, this exception is triggered if the logon status is not enabled.

3000

RPC interface does not exist or is down

In the environment corresponding to the current workspaceId, the mobile application corresponding to the appId does not have an API service configured with the operationType, or the API service is not in the Open state.

3001

The request data is empty.

The requestData in the client request data is empty. Check whether the client RPC service is normal. Make sure that the gateway service is initialized on the iOS client.

3002

Wrong data format

There is a problem with the RPC request format. Public cloud users can view details in the server log gateway-error.log.

3003

Data decryption failed

Data decryption failed.

4001

Service request timeout

MGS calls the business system service timeout. If the backend business system is overloaded, you need to check the running status of the backend system. If the timeout setting is unreasonable, you can adjust it appropriately. Note: The default timeout period is 3s.

4002

Remote call service system exception

An exception occurred when MGS called the business system service. Public cloud users can view details in the server log gateway-error.log.

4003

API group HOST exception

An UnknownHostException exception occurred when MGS called the HTTP business system service. Check whether the domain name configured for the API group exists.

5000

An unknown error occurred.

Other serious errors. Public cloud users can view details in the server log gateway-error.log.

7000

No public key set

The wireless bodyguard in the mobile APP does not have the key corresponding to the appId or the gateway cannot obtain the signature key corresponding to the appId.

7001

Insufficient parameters for signature verification

The gateway server fails to verify the signature.

7002

Signature verification failed

The gateway server fails to verify the signature.

7003

Signature verification-timeliness failed

The ts timestamp of the API request input parameter exceeds the time validity set by the system. You need to check whether the client time is the system time.

7007

Check signature-the ts parameter is missing

The API request is missing the signature verification ts parameter.

7014

Sign verification-the sign parameter is missing

The API request does not have the sign parameter. In most cases, the client fails to sign data. As a result, the sign parameter is missing. Please check the client wireless bodyguard picture is correct.

8002

Cross-domain precheck requests (CORS preflight)

Cross-domain precheck requests.

Business-side result code

The following result code allows you to view the error message inside the business system server.

You can view the ~/logs/mobileservice/monitor.log logs on each business system to determine the exception details.

Response code

Applicable Agreement

Description

Explanation

6000

MPC, DUBBO

RPC-Target service not found

The published service cannot be found, the server cannot be accessed, or the service has been migrated.

6001

MPC, DUBBO

RPC-Target method not found

The method in the published service cannot be found.

6002

MPC, DUBBO

RPC-Incorrect number of parameters

The number of input parameters, which is not equal to the number of declared parameters.

6003

MPC, DUBBO

RPC-Target method not accessible

The target method cannot be called.

6004

HTTP, MPC, and DUBBO

RPC-JSON parsing exception

HTTP: An exception occurred while converting the RPC parameter to a backend HTTP request parameters. MPC/DUBBO: Failed to deserialize the RPC JSON-formatted data into a business parameters object.

6005

MPC, DUBBO

RPC-invalid parameters when calling target method

Parameters are invalid when you call a reflection operation.

6007

MPC, DUBBO

RPC-Authentication logon service unavailable

The authentication login port is not implemented in the SPI package or the authentication login port configuration is incorrect.

6666

HTTP, MPC, and DUBBO

RPC-Business throws exception

HTTP: The HTTP status code returned by the backend system is not equal to 200. MPC/DUBBO: exceptions thrown by the business side. RPC cannot be handled, unified as a business exception.

Android client result code

Response code

Description

Prompt copy

0

Unknown error.

Unknown error. Please try again later.

1

Client cannot find communication object, Transport not set

A network error occurred. Please try again later.

2

The client has no network, such as the user has disabled the network or disabled the network permissions of the application

Network cannot connect

3

SSL-related errors, including SSL handshake errors and SSL certificate errors

The client certificate is incorrect. Check whether the time setting of the mobile phone is accurate.

4

Client network connection timeout, TCP connection timeout, the current timeout period is 10s

Poor network

5

Scenarios where the network speed of the client is too slow, data read and write times out, and socketTimeout

Poor network

6

The client requests no response from the server, NoHttpResponseException

A network error occurred. Please try again later.

7

Client network IO error, corresponding to IOException

A network error occurred. Please try again later.

8

Client network request scheduling error, execution thread interruption exception

A network error occurred. Please try again later.

9

Client processing errors, including serialization errors, annotation processing errors, and thread execution errors

A network error occurred. Please try again later.

10

Client data deserialization error, server data format error

A network error occurred. Please try again later.

13

Request interruption error, such as network request will be interrupted when thread is interrupted

A network error occurred. Please try again later.

15

Client network authorization error, HttpHostConnectException,Connection to xxx refused, no network or connection refused by corresponding server

Network cannot connect

16

DNS resolution error

The network cannot be connected. Please try again later.

18

Network traffic limit, client traffic limit, network requests are throttled when the client request traffic exceeds the threshold

Network traffic limit. Please try again later.

Code ≧ 400 and code < 500

HTTP response code is 4xx

Network cannot connect

400 > code≧ 100 and 500 < code < 600

HTTP non-successful response codes

The network cannot be connected. Please try again later.