iOS: Transitioning to Token-Based Configuration for APNs

Q: What is the procedure for migrating from a certification-based connection to a token-based configuration for APNs that is specifically designed to support live activities?

A: To migrate from a certification-based to a token-based configuration for Apple Push Notification service (APNs), refer to our iOS token-based configuration guide. This migration process does not require any changes to the end user device tokens.

Q: What potential impacts can this transition have on our existing setup, including possible downtime, compatibility concerns, or additional adjustments required on our part?

A: The changes will be immediately effective upon updating the application configuration in your application config in Pushwoosh. Compatibility issues are unlikely to occur since the changes are on the APNs side.

Q: Can you provide relevant documentation or resources that can guide us through the implementation process seamlessly?

A: Yes, you can refer to the iOS token-based configuration guide. When implementing the changes, ensure that the Apple Developer Team ID, Bundle ID, and Gateway type (Sandbox or Production) match your current certificate-based configuration.

For a seamless experience, after updating the configuration, perform a test push to a small segment of users or to your test devices to make sure that notifications were sent by the APNs gateway without errors.

Go to the Message History, find the notification you sent, then go to the Delivery Report section of the notification. You'll see the number of successful sends and any error messages if they occur.

Q: How can we get support if we face any challenges during the migration process?

A: You can contact support at any time. However, the migration process is quite straightforward and is detailed in the provided guide, ensuring a seamless transition with minimal disruption to services.