[FAQ] access the HMS core push service, and the server sends messages. Cause analysis and solutions of common error codes

HMS Core​ ​ Push service ​​ Support developers to use HTTPS Access Agreement Push Server side , You can send downlink messages from the server to the terminal device . This article summarizes the most common messages sent by servers 6 An error code , It also provides cause analysis and solutions , Developers who encounter similar problems need to know about it .

Error code one ：80200001," Oauth Authentication error "

Cause analysis ：

1. The message sent was not added Authorization The request parameter or value is empty .

2. application A Of APPID Applied Access Token, But for applications B Push message , This error code will also appear .

apply Access Token

Send message

resolvent ：

1. Troubleshooting request HTTP Whether there is a reference in the head Authorization Request parameters .Authorization The acquisition method can   Reference documents 、 Downlink message API can   Reference documents .
2. obtain Access Token The use of APPID And sending messages APPID Need to be consistent .

Error code two ：80300007,"Token Invalid error "

Cause analysis ：

1. token illegal ,token More or less characters , For example, there is more space in the following figure .

2. For application A Send message ,token But application B Of , This situation is also one of the reasons .

resolvent ：

1. Check token Is the parameter correct ;
2. Make sure to send messages using token, It is obtained from the target application

Error code three ：80300010," In message body Token The quantity does not meet the default value "

Cause analysis ：

1. Developers will “message” Misspelled fields , In the example diagram message There are too many fields at the end 'r';
2. token Not in the right place , Field structure problem ;
3. Issued token The quantity exceeds the limit , or token It's empty .

resolvent ：

1. Make sure message、token The field is written correctly ;
2. message Field contains token, And "android" At the same level ;

3. token The quantity of should be in 1-1000 individual , confirm token Number of parameters , Please refer to ​ ​ Reference documents ​​.

Error code four ：80200003,"Oauth Token Be overdue "

Cause analysis ：

1. Authorization In the request parameter value Access Token Has expired
2. The request parameter value is incorrect , More or less other characters .

resolvent ：

1. Access Token Valid for one hour , If the time limit is exceeded , You need to retrieve and use the latest Access Token Send message . Recapture Access Token Method   Refer to article files
2. Ensure that the Access Token Consistent with the obtained , Copy Access Token Escape characters appear when , Need to put “\/” Revert to “/”.

Error code five ：80100016," The message contains sensitive information "

Cause analysis ：

This error message indicates that the content of the push message contains sensitive information

resolvent ：

1. Since no sensitive thesaurus is provided , Developers need to detect the content by themselves ;
2. Developers can access twitter , After the message is approved by twitter , Huawei will not conduct a second audit . The process of accessing twitter can   Reference documents .

matters needing attention ：

1. After approval of tibian , You need to add the results returned by tibian to Huawei Review Field result In the object , Only in this way can Huawei know that the message has passed the review , Huawei will not conduct a second audit .

Log in and copy

      
      

       
       "review": [
       
       
        {
       
       
            "reviewer": "tuibian",[]()
       
       
            "type": 0,
       
       
            "result": {
       
       

       
       
                // The following is the result returned by tibian 
       
       
                "code": 200,
       
       
                "data": {
       
       
                    "auditEngine": "t****ine",
       
       
                    "auditId": "0f74b*******0b3f490d",
       
       
                    "labels": []
       
       
                },
       
       
                "msg": "Pass",
       
       
                "sign": "MEQCIBHc********IqLjw=="
       
       

       
       
            }
       
       
        }
       
       
    ]
       
       
}
      
      
      
      

       
       
1.
       
       
2.
       
       
3.
       
       
4.
       
       
5.
       
       
6.
       
       
7.
       
       
8.
       
       
9.
       
       
10.
       
       
11.
       
       
12.
       
       
13.
       
       
14.
       
       
15.
       
       
16.
       
       
17.
       
       
18.
       
       
19.
       
       
20.
      
      

2. Not to put the whole message body on twitter “content” Field , What needs to be reviewed is “message” What's in it , At the same time, press ASCII The code is sorted in ascending order and then converted to string format for approval .

Log in and copy

      
      

       
       {
       
       
    "validate_only":false,
       
       
    "message":{
       
       

       
       
        // The following parts need to be reviewed 
       
       
        "notification":{
       
       
            "title":"message title",
       
       
            "body":"message body"
       
       
        },
       
       
        "android":{
       
       
            "collapse_key":0,
       
       
            "notification":{
       
       
                "click_action":{
       
       
                    "type":2,
       
       
                    "url":"https://example.com"
       
       
                }
       
       
            }
       
       
        },
       
       

       
       
        "token":[
       
       
            "pushtoken1"
       
       
        ]
       
       
    }
       
       
} 
      
      
      
      

       
       
1.
       
       
2.
       
       
3.
       
       
4.
       
       
5.
       
       
6.
       
       
7.
       
       
8.
       
       
9.
       
       
10.
       
       
11.
       
       
12.
       
       
13.
       
       
14.
       
       
15.
       
       
16.
       
       
17.
       
       
18.
       
       
19.
       
       
20.
       
       
21.
       
       
22.
       
       
23.
       
       
24.
      
      

3. Due to the cumbersome audit process , It is suggested to reduce the use of distribution fields , This operation is simpler and will avoid the occurrence of 80100018 Error code , This error code means that the message body sent to the third-party organization for review is inconsistent with the message body when it is issued .

Error code six ：sub_error":57303,"error_description":"appid is overload blocked","error":1302

Cause analysis ：

Too many requests access_token Flow controlled , The flow control threshold is 1000 individual /5 minute .

resolvent ：

Adjust the request logic ,access_token Valid for one hour , No need to apply frequently . Flow control 5 Reset in minutes , You can apply again . more access_token Relevant restrictions can ​ ​ Reference documents ​​.

Learn more >>

visit ​ ​ Official website of Huawei developer Alliance ​​ obtain   Development guidance document
Huawei mobile service open source warehouse address ： GitHub、 Gitee

Pay attention to our , The first time to understand HMS Core Latest technical information ~