I submitted a bug report, FB9889200. Would be great if everyone can do so, so that Apple reacts more quickly.

In my case it seems that Apple just changed the public link under the hood. The link has been the same for as long as I can remember and now it was just changed without any communication. Not the nicest experience @ Apple.

Apple seems to have fixed it again. Can anyone else confirm? @MatKuznik @dkdd

Created another bug report FB9735670 @edford

Anyone else running into the problem AGAIN as well? We also had the problem back then in August, then it started working again, and now it seems to be broken again. I applied the same UUID fix as back then and that does the trick.

Is there any update on this? Seems like this is still an issue with the latest Xcode (12.5.1)

You probably figured this out by now, but as far as I understand you are fine with an "HTTP/2 provider certificate". The Mar 31, 2021 deadline only affects the "legacy binary protocol", in other words certificates that have been created "a long time ago". From what I can see, through the Developer Portal you are only able to create APNs certificates based on HTTP/2, but I'm not an expert on the field. Like I didn't see a checkbox that let's you select "HTTP/2" or something. Apple Push Notification service SSL (Sandbox & Production) Establish connectivity between your notification server, the Apple Push Notification service sandbox, and production environments to deliver remote notifications to your app. When utilizing HTTP/2, the same certificate can be used to deliver app notifications, update ClockKit complication data, and alert background VoIP apps of incoming activity. A separate certificate is required for each app you distribute. In my opinion Apple is doing a not so great job with how they communicate those things. Yes, there is this article - https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns which describes both Tokens and Certs, but they do a poor job comparing "legacy certificates" with "HTTP/2 certificates". Because a lot of blogs out there used to compare things like this: Auth Tokens (HTTP/2) vs. the legacy way (certificates) But as we have seen now, the certificate situation is the one that needs to be distinguished more granularly.

does anybody else think it is sdk 14 issue? I don't think so. The linked issue is talking about Xcode 12 with iOS 14 SDK, while here we have exactly the opposite - at least in my case - Xcode 11.7 with iOS 13 SDK. Also other people explicitly mentioned being on Xcode 11 still.

Same here. It started failing for me 3 days ago, and I thought it was something about the setup. Two devices, several re-boots and several Sandbox accounts later I was pretty sure it was not the setup on my side. Apple please fix this. This cost me a lot of time and nerves. Not all devices/setups are iOS 14/Xcode 12 only. Thank you. Xcode 11.7.0 iOS 13.7