Based on the date you started having this issue, it would mean you were still using the legacy Binary Interface which was retired March 31st, 2021 (https://developer.apple.com/news/?id=c88acm2b). And was finally shut down on April 2nd.
This requires you to migrate your push servers to use the HTTP/2 API. Any push servers still using the legacy interface will be unable to connect to APNs, resulting in Push Notifications not working.
More information about the HTTP/2 provider API can be found in these two WWDC sessions:
You can read more about the new APNs Provider API here:
https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns/
If you have issues after migrating to the new interface, or have technical questions about the migration, we are happy to help troubleshoot your push requests once you have started using the HTTP/2 protocol. Please understand that we are unable to help with the specifics of your server side implementation. Unfortunately we also cannot make recommendations on which 3rd party resources to use to make this transition.
Developers using the legacy protocol had been allowed to use it past the deadline to minimize disruptions, but if you are having issues now, it is time to switch. The legacy protocol is no longer supported, and we would not be able to say if and when your specific issue might be addressed. There are no more extensions or exceptions for your app once you start having problems. Moving to the new HTTP/2 protocol as explained above is your only option.
If you run into issues after converting to HTTP/2 and would like us to help debug, we will need the apns-id of your failed push requests. So, make sure you are logging that data along with other details.
Argun Tekant /
DTS Engineer /
Core Technologies
