Blog
ENGINEERING

Get Your iOS App Ready for the 2025 Apple Push Notification Service Server Certificate Update

Mike Miller

December 13, 2024

APNS Apple Push Notification Service Update 2025

Table of contents

*Update*

Update

We’re excited to confirm that Courier customers are unaffected by this update. Notifications sent via APNS with P8 keys or P12 certificates work seamlessly, and no changes are required.

Read more about what we tested

---

What’s Changing

Apple is updating its Push Notification service (APNs) certificates to use the USERTrust RSA Certification Authority (SHA-2 Root). Key dates include:

  • Sandbox: January 20, 2025
  • Production: February 24, 2025

To keep push notifications working, you must update your server’s Trust Store to include the new certificate authority. Both old and new certificates should remain trusted during the transition. Read Apple’s official announcement here.

We’ll update this post with details for `node-apn` and similar packages after January 20. Be sure to bookmark this post!

Using Courier? No Changes Are Needed

Courier has already implemented these changes, so you don’t need to worry. Notifications will flow seamlessly with no extra work on your part. Courier also lets you design and manage notification templates effortlessly. Explore Courier’s resources to get started:

If you are not using Courier, here's what you need to do:

How to Update Your Server

If you’re updating manually, follow these steps:

Step 1: Download the New Certificate

Get the USERTrust RSA Certification Authority (SHA-2) certificate from Apple’s official site or a trusted source.

Step 2: Update Your Trust Store

Unix/Linux Servers:

  1. Locate your ca-certificates directory (e.g., /etc/ssl/certs/).
  2. Copy the certificate:

Copied!

sudo cp /path/to/USERTrustRSA.crt /etc/ssl/certs/
  1. Update certificate hashes:

Copied!

sudo c_rehash
  1. Restart your server.

Windows Servers:

  1. Open Microsoft Management Console (MMC) and add the Certificates snap-in.
  2. Navigate to "Trusted Root Certification Authorities."
  3. Right-click and select "Import," then follow the wizard.
  4. Restart your server.

Step 3: Test the Update

  • Sandbox Testing: Begin testing on January 20, 2025. Check server logs for SSL errors or issues.
  • Monitor Logs: Regularly review logs to catch problems early.

For .p8 Key Users

If you’re using .p8 keys for APNs authentication, no changes are required for your app’s code. However, you still need to:

  • Update your server’s Trust Store.
  • Test notifications in sandbox mode starting January 20.

Risks of Not Updating

Skipping these updates may cause:

  • Push Failures: Notifications won’t be delivered.
    • Solution: Test thoroughly in sandbox mode.
  • SSL Errors: Unreliable connections due to missing certificates.
    • Solution: Use SSL tools like SSL Labs to verify configurations.
  • User Impact: Downtime can frustrate users and hurt engagement.
    • Solution: Monitor closely during the transition.

Tips for a Smooth Transition

  1. Start Early: Test in the sandbox environment ahead of production updates.
  2. Trust Both Certificates: Load old and new certificates during the transition.
  3. Document Testing: Record your tests and fixes for reference.

Key Dates to Remember

  • Sandbox Testing Starts: January 20, 2025
  • Production Update: February 24, 2025

By preparing now, you’ll ensure your push notifications continue without interruption. If you need help, consult Apple’s documentation or contact your notification provider. Let’s make 2025 a seamless year for your app’s notifications!

Similar resources

mcp vs cli for ai agents
Engineering

Your AI agent already knows how to use a terminal. Why CLIs beat MCP servers

LLMs already know how to use a terminal. We maintain both an MCP server and a CLI at Courier, and the difference tells you something about where AI tooling is heading.

By Mike Miller

March 13, 2026

EU data residency and translations and gdpr
EngineeringCourier

EU Data Residency for Notifications: What Engineering Teams Need to Know

Courier supports EU data residency through a dedicated datacenter in AWS EU-West-1 (Ireland), with full API feature parity, same-workspace dual-region access, built-in GDPR deletion endpoints, and localization support for multilingual notifications. Engineering teams can switch to EU hosting by changing a single base URL with no workspace migration or downtime required.

By Kyle Seyler

March 09, 2026

courier and expo push notifications
GuideEngineering

Expo Push Notifications: The Complete Implementation Guide (SDK 52+)

Expo push notifications are alerts sent from a server to a user's phone, even when the app isn't open. To set them up, install the expo-notifications library, ask the user for permission, and get a unique push token for their device. Your server sends a message to Expo's push service with that token, and Expo delivers it through Apple or Google. Push notifications only work on real phones, not simulators. Local notifications are different — they're scheduled by the app itself for things like reminders. You can also route Expo push through services like Courier to add email, SMS, and Slack fallbacks.

By Kyle Seyler

February 24, 2026

Multichannel Notifications Platform for SaaS

Products

Platform

Integrations

Customers

Blog

API Status

Subprocessors


© 2026 Courier. All rights reserved.