Overview
This topic describes how to troubleshoot and resolve failed pushes on iOS.
Details
Push fails during initial integration
If a push fails during the initial integration, review the following steps to ensure that your configuration is correct:
Before you integrate the push SDK, confirm that the push certificate is configured correctly. For more information, see Configure an iOS push certificate.
During the integration, follow the instructions in Configure the iOS SDK.
During development, refer to the iOS push demo to accelerate your development. If you want to compile and run the demo, modify it according to the instructions in its README file.
Enable debug logs. For more information, see Enable debug logs. Troubleshoot based on the error messages in the logs. For more information, see iOS error codes.
If you have problems retrieving extension parameters for iOS notifications, see What do I do if I cannot get extension parameters for notifications on iOS?.
After you attach a tag to a device, the server pushes messages based on that tag. Note that it takes up to 10 minutes for the tag to take effect. For more information, see iOS API reference.
Search for relevant keywords in iOS SDK FAQ to check for descriptions of similar issues.
An issue occurs after successful integration
If a push notification fails, see Troubleshooting steps for undelivered push notifications on iOS.
If a push message fails, see Troubleshooting steps for failed push messages on iOS.
Self-service troubleshooting tool
Log on to the EMAS console. In the navigation pane on the left, click Mobile Push. Select your product and application. Then, in the navigation pane, click Troubleshooting Tool.
Enter a message ID or device ID to run a query. Use the query results to locate and resolve the issue. For more information, see Troubleshooting Tool.
If the preceding steps do not resolve the issue, you can obtain assistance using the following methods:
Join our DingTalk group to ask questions:
DingTalk download link: Click to download
DingTalk group number: 35248489
Alternatively, you can submit a ticket. When you submit the ticket, select the Mobile Push category.
When you report an issue, include the following formatted information to help Alibaba Cloud technical support locate the issue more quickly. Items marked with an asterisk (*) are required.
Your operation:
Abnormal behavior:
Device platform (Android or iOS), model, and OS version number:
Push type (message or notification):
Push method (all, account, device, tag, or alias):
* appkey:
* Message ID (available in the console):
* deviceID (available in the console):
* requestID:Applies to
Mobile Push