iOS configuration options

This section provides step-by-step instructions for configuring your iOS application to enable messaging services using Pushwoosh. Choose between certificate-based or token-based configuration depending on your project requirements.

Learn how to configure Pushwoosh for iOS using certificate-based authentication for APNs (Apple Push Notification Service).

Set up Pushwoosh with token-based authentication for APNs, offering a more secure and efficient alternative to certificates.

When configuring iOS push notifications in Pushwoosh, you must authenticate with Apple Push Notification service (APNs). There are two supported methods:

1. .p12 certificate: the traditional, certificate-based approach.
2. .p8 key: the modern, token-based method recommended by Apple.

This guide will help you determine which method best fits your use case.

Pros:

• Widely supported.
• Allows separate certificates for development and production.

Cons:

• Certificates expire and require renewal. Failure to renew can disrupt push delivery.
• More complex to manage.

Pros:

• No renewals required, reducing maintenance overhead.
• Easier to generate and integrate.
• One key works across projects.
• Recommended by Apple and Pushwoosh.

Cons:

• If compromised, all associated apps are at risk. Secure your .p8 key properly.

We recommend using the .p8 key method for all new projects. It is simpler, more scalable, and aligned with Apple’s best practices.

Use .p12 certificates only if:

• You have existing infrastructure dependent on .p12 certificates.
• You require strict environment separation that cannot be achieved with a .p8 key.