iOS VoIP推送异常咨询：特定用户无法接收推送排查求助

Hey Andrew, sorry to hear you're stuck with this tricky one-off VoIP push problem—these edge cases are always frustrating, but let’s walk through the possible causes and fixes step by step.

Could Your Payload Be the Culprit? #

Absolutely, payload issues are a common (and easy to miss) cause of dropped pushes, especially for VoIP:

• Payload Size Limits: VoIP pushes have a stricter 5KB size limit (compared to 4KB for standard pushes). If your payload exceeds this, APNs will silently discard it without notifying your backend. Calculate the byte size of your full payload to rule this out.
• Incorrect Format: Looking at your payload snippet, you’ve placed approvalMessageId inside the aps dictionary—this is a mistake! Custom data should live in the top-level dictionary, not nested under aps. APNs only processes standard keys in aps, and unknown keys here can cause parsing failures, especially on older iOS versions that have less tolerance for invalid payloads. Your corrected payload should look like this:

  {
    "aps": {
      "alert": "test",
      "badge": 0,
      "category": "..."
    },
    "approvalMessageId": 0
  }
  

  Even if other users receive pushes fine, this formatting quirk might trigger a failure on this specific user’s device (e.g., an older iOS version that rejects non-standard aps keys).

Can You Get Push Status from Apple? #

Yes, Apple provides several ways to track push delivery status:

• HTTP/2 API Responses: If your backend uses the APNs HTTP/2 API, every push request returns a status code and detailed error message. Check your backend logs for the request targeting this user—codes like 400 (invalid payload), 413 (payload too large), or 404 (invalid device token) will point directly to the issue.
• Device Token Validation: APNs will return a BadDeviceToken error if the user’s token is invalid (e.g., they reinstalled the app without your backend updating the token). Even if you’re using the same IPA/cert, individual device tokens can become stale.
• Feedback Mechanisms: For older protocols, Apple’s Feedback Service lists tokens that are no longer valid, but with HTTP/2, this is integrated directly into response codes. Make sure your backend is logging these responses thoroughly.

Similar Issues I’ve Seen (and Fixed) #

I’ve dealt with a few one-off VoIP push failures like this:

• Background Refresh Permissions: The user might have disabled Background App Refresh for your app (Settings > [Your App] > Background App Refresh) or enabled Low Power Mode, which disables background activities. VoIP pushes rely on this permission to maintain a persistent connection to APNs—without it, pushes won’t reach the app.
• Network Restrictions: Some corporate or public Wi-Fi networks block APNs ports (5223 for VoIP pushes). Ask the user to test on cellular data to rule this out.
• Stale APNs Connection: On older iOS versions, if the user force-quits the app, the persistent VoIP connection to APNs might not re-establish until they manually open the app again. Have them try fully closing and reopening the app.

Next Steps to Debug #

1. Fix your payload format to move custom data outside the aps dictionary, and verify it’s under 5KB.
2. Pull the exact APNs response logs for this user’s push requests—this will likely give you the most direct clue.
3. Guide the user through checking Background App Refresh, Low Power Mode, and testing on a different network.
4. If all else fails, have them reinstall the app or reset their device’s network settings (this can fix stuck APNs connections).

内容的提问来源于stack exchange，提问作者Andrew