[iOS][3.4.0] Campaigns on iOS always received an error of `APNS disallowed topic`

[devphilipcesar]

After we migrated to 3.3.0 and 3.4.0, we noticed that we no longer received Push Notifications from a Campaign on iOS. Since the removal of the setPushToken(value, type) API and replacing it with setFCMPushToken to save the APNS Token generated, we now experience this issue.

Previously we use the setPushToken to saved the APNS token associated to a Clevertap account. Kindly advice on how are we going to resolved this issue.

PS: During the testing phase sending a test push notification on an iOS simulator and device. We can received a push notifcation.

[nishant-clevertap]

Hi @devphilipcesar

Are you not getting push from older campaign or even with newly created ones?

[devphilipcesar]

@nishant-clevertap both older and newly created campaigns.

[nishant-clevertap]

@devphilipcesar Thanks for the information, I will check this in our sample app and will update you.

[devphilipcesar]

@nishant-clevertap I also tried to tried to downgrade back to 3.2.0 since that was the last known working version and tested it today. Still, I got the same issue of APNS disallowed topic even if during the testing phase both the emulator and device able to received a test push notification here

[Sonal-Kachare]

@devphilipcesar
Could you please share how you're setting up push notifications, along with relevant code snippets?
And how are you setting APNS push token in js code?
We’ll try to reproduce the issue in our sample app and get back to you.

[jbagaresgaray]

@devphilipcesar Could you please share how you're setting up push notifications, along with relevant code snippets? And how are you setting APNS push token in js code? We’ll try to reproduce the issue in our sample app and get back to you.

Hi @Sonal-Kachare sure2x... so basically we're using the react-native-firebase cloud messaging here and this is how we save the Push token associated to the user.

import messaging from '@react-native-firebase/messaging';
import CleverTap from 'clevertap-react-native';
.
.
.
.

if(messaging().isDeviceRegisteredForRemoteMessages) {
    if (Platform.OS === 'ios') {
       const apnsToken = await messaging()?.getAPNSToken();
       CleverTap.setFCMPushToken(apnsToken);
    } else {
       const fcmToken = await messaging()?.getToken();
       CleverTap.setFCMPushToken(fcmToken);
    }
}

Once the token is saved, this is how it looks on the Dashboard

I even tested it and I was able to receive a push notification via the APNS Development push mode.

[devphilipcesar]

Hi @Sonal-Kachare @nishant-clevertap Good day to you... I hope you're all doing well. I would like to follow up on the status of this issue, as we're currently facing some problems with our marketing metrics, and we can't reach out to our iOS users.

[devphilipcesar]

Hi @Sonal-Kachare @nishant-clevertap Good day to you... I hope you're doing great.

I tested the latest clevertap-react-native SDK v3.5.0, and still our iOS app could not receive a Push Notification instead it's showing this error message when doing a test push notification of our app

As you may see, the APNS Token is saved correctly

and it matches to the Push token shown on the popup

Meanwhile on Channel/Mobile Push -> iOS Tab, the APNS push mode is already set to Production

In case you may need my Clevertap ID: -v5931e9a9c7b54a7fb2fa8bb6040a6517

[Sonal-Kachare]

@devphilipcesar Are you trying to receive PushNotifications on debug / dev app?
You need to change APNS push mode to Development

https://docs.clevertap.com/docs/troubleshooting-faqs-push-notifications#apns-topic-disallowed

[devphilipcesar]

Hi @Sonal-Kachare as mentioned above, our app where able to receive a push notification on APNS push mode development.

The issue happens only when the APNS push mode is production

Also note that our app is fully working on 3.2.0 but right after we upgraded the SDK to 3.3.0 and later, that's where we no longer receiving any push notification