[iOS] Device Token Not For Topic error

Issue

We're encountering the "Device Token Not For Topic" error. Now we cannot receive the push notification on our devices and the amount of our iOS devices has decreased.

Troubleshooting

Issue Overview

The DeviceTokenNotForTopic error occurs when Apple Push Notification service (APNs) identifies a mismatch between the push notification token and the app’s topic (usually the App ID / Bundle ID). This mismatch prevents notifications from being delivered to devices.

Typically, this happens when:

• The token issued to a device is linked to one Apple App ID, but the APNs credentials uploaded to Pushwoosh belong to a different App ID.
• APNs attempts to send the notification, but the topic (App ID) does not match the token on the device, triggering the error.

Step 1: Identify which APNs authentication method your project uses

Pushwoosh supports two APNs authentication methods, and the fix differs:

• Token-based (.p8 authentication key) — the method recommended by Apple and Pushwoosh, and the default for new projects.
• Certificate-based (.p12 push SSL certificate) — the legacy method, kept for existing setups.

Check Settings → Platform Configuration → iOS in the Control Panel to see which one is configured.

Step 2: Verify App ID consistency

• Token-based (.p8): confirm the Bundle ID entered in Pushwoosh exactly matches the bundle identifier of the app that produced the device tokens, and that the Key ID and Team ID belong to the same Apple Developer account as that app.
• Certificate-based (.p12): confirm the Apple App ID in the provisioning profile used to build the app matches the App ID the push SSL certificate was generated for, and that the certificate came from the same Apple Developer account.

Step 3: Correct the credentials

If you find a mismatch, re-upload the correct credentials for that App ID: generate a new .p8 key (or re-issue the .p12 certificate) from the Apple Developer account that owns the App ID, then reconfigure the iOS platform in Pushwoosh. Once the correct credentials are in place, delivery resumes and the number of active iOS devices recovers gradually.

Step 4: Reconfigure the iOS platform (if necessary)

If you no longer have access to the Apple Developer account originally used, reconfigure your iOS push settings from scratch under the correct account. We recommend switching to token-based (.p8) configuration at that point — .p8 keys do not expire, work across environments, and are required for iOS Live Activities.

See also: Pushwoosh iOS SDK Setup Guide and iOS configuration options (.p12 vs .p8).