iOS Error: No APNS token specified before fetching FCM Token

[gz1992]

Hey guys, I am creating a new app using version 0.70.6 and @react-native-firebase/messaging ^17.3.1

But I have an old react native app version 0.62.3 using @react-native-firebase/messaging ^15.6.0 on App Store.

I am facing some problems regarding FCMToken, especially this one: No APNS token specified before fetching FCM Token.
When I try to login in my app. For Android, everything went well, but iOS didn't.

Does anybody know how can I test on my computer without getting this "No APNS token specified before fetching FCM Token" problem?

OBS: My Xcode is updated properly, because on my TestFlight app, I can login and also send push notifications

[gz1992]

I think I found the problem. I changed the way my APNS token is used in my iOS, via firebase. And I need to force the update of all FCMToken that are used in the previous way. Does somebody know how to do it??

[gz1992]

Found it... As FCMToken is related to the user device, when I changed my certificate on firebase, some users that couldn't update their token couldn't access my platform. It is important to mention that the users had permission but couldn't get token

messaging().hasPermission().then(permission => {})

As a result, I needed to force the registration of their device by:

await messaging().registerDeviceForRemoteMessages();
return messaging()
    .getToken()
    .then(token => token)

[hadanghuy]

Bạn có phần sửa cụ thể ở chỗ nào không?

[tuannha01]

@gz1992 Can you tell hime where to updated 😄

[gz1992]

hey @tuannha01 and @hadanghuy , in my case, we migrated and updated the firebase lib, and we had a problem with the fcmtoken, the cellphone was already registered... so instead ASKING AND IDENTIFING THE PERMISSION

messaging().hasPermission().then(permission => {})

i needed to force the device registry again, through this code:

await messaging().registerDeviceForRemoteMessages();
return messaging()
    .getToken()
    .then(token => token)

[mhassanmalik]

My issue was resolved by adding onRegister() inside PushNotification.configure(). I was not setting the retrieved APNS token in messaging() before asking for the FCM token.

onRegister(token) {
  if (Platform.OS === 'ios') {
    messaging().setAPNSToken(token.token);
  }
}