You can use the troubleshooting tool to troubleshoot message push exceptions such as message delivery or push failures and query device details (including the associated accounts and tags) through an account or token.
A developer successfully pushes a message to the testing device in the console, but this message is not displayed in the notification bar of the device. Using a token to query the device in the troubleshooting tool detects that the notification bar is disabled. Enable it on the device, trigger registration again, and send a message to the device again. The message is now displayed in the notification bar.
An operator fails to push a message to a specified account. Using the account to query the token in the troubleshooting tool detects that the account hasn't been associated with a token yet. Please submit a ticket to check whether the API for Android or iOS was called to bind an account.
After completing the TPNS integration, a developer pushes a message to a certain batch of device tokens, but an online user reports that the push message hasn't been reported. Querying the obtained token and
pushID of the user in the troubleshooting tool detects that the token is not in the push list.
- Account: refers to the unique ID of the user bound to the token, including
- Token list: displays tokens in reverse chronological order by binding time. A maximum of 10 tokens are listed in a page. If the account is bound to multiple devices, the message will be pushed to the last device bound to this account. To push the message to all devices bound to this account, please change the push settings through the console or the API.
pushid(required) and the device token to be queried (required), and click Query to view the troubleshooting results.
- Select Push Management > Task List on the left sidebar to get the
PushIDto be queried.
- Get it from the response parameter of the push API.
pushIDand token for assistance.
<uses-library android:name="org.apache.http.legacy" android:required="false"/>