-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Apple's APNS server certificates #10
Comments
cc @alltheseas, we don't need to do this right now, but we need to pay attention to some of these dates. I set a reminder for myself on January 20th 2025, but please feel free to label/schedule this as you need! |
On Fri, Dec 06, 2024 at 01:00:10AM -0800, Daniel D’Aquino wrote:
cc @alltheseas, we don't need to do this right now, but we need to pay attention to some of these dates. I set a reminder for myself on January 20th 2025, but please feel free to label/schedule this as you need!
we ready for this?
|
Not yet. My plan is to start testing this on the Sandbox from January 20th, so that we can see whether we are impacted, and so that we can test this out |
Added to the next sprint |
From Apple:
As we announced in October, the Certification Authority (CA) for Apple Push Notification service (APNs) is changing. APNs will update the server certificates in sandbox on January 20, 2025, and in production on February 24, 2025. To continue using APNs without interruption, you’ll need to update your application’s Trust Store to include the new server certificate: SHA-2 Root : USERTrust RSA Certification Authority certificate.
To ensure a smooth transition and avoid push notification delivery failures, please make sure that both old and new server certificates are included in the Trust Store before the cut-off date for each of your application servers that connect to sandbox and production. At this time, you don’t need to update the APNs SSL provider certificates issued to you by Apple.
If you have any questions, please contact us.
The Apple Developer Relations Team
We need to check whether we need to manually update the certificates.
The text was updated successfully, but these errors were encountered: