Some users stop to receive notification after we migrate to APNS HTTP/2 interface

Originator:changxg
Number:rdar://34804965 Date Originated:10/3/2017
Status:Open Resolved:
Product:iOS + SDK Product Version:
Classification:Notifications Reproducible:Some time
 
Summary:

Last week after we started to use APNS HTTP/2 API (originally we use their legacy API) to send notifications to Yahoo Mail, and some users started to complain that they cannot receive notification, even though we have successfully delivered the notification to APNS HTTP/2 and get 200 response. Looks like those devices are left in some odd state after we migrated the traffic from legacy API to HTTP/2 API. One workaround we figured out is to uninstall/reinstall the app to get a new APNS push token, but I'm not sure if this the right solution and if this can address all user's problem.

The apps I'm talking about are 'com.yahoo.Aerogram' and 'com.yahoo.Aerogram-dogfood'.

One specific example is for 'com.yahoo.Aerogram-dogfood', push token '6138bceff6041383d3f7df5c28261bcc6e786d89803e47cf681cd85405dd9614', we keep get 200 today from both the legacy APNS API and the new APNS HTTP/2 while the user get nothing.


Steps to Reproduce:

N/A

Expected Results:

User should continue to receive notification, or we should get a new token from App and get error from APNS when we keep sending notification to the old token.

Actual Results:

The App still get the same token, when we send notification to APNS it also return success, while user get nothing.


Version/Build:


Configuration:

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!