React-native-firebase: Firebase.messaging().onTokenRefresh doesn't fire

[stefanedberg]

Issue

I'd like to use Firebase for push notifications and this is my setup:

Firebase.messaging().onTokenRefresh(token => {
            storeNotificationToken(token);
});

Firebase.messaging().requestPermissions();

Firebase.messaging().onTokenRefresh never fires and according to Xcode logs it seems like it tries to fire the event before my listener is registered, even though I'm doing it as early as I possible (even tried index.ios.js).

Just to clearify, this is when the app is installed on the phone and before I accepted the permissions dialog.

Using getToken() manually and sending push notifications works just fine, but I shouldn't need to call getToken, right?

Xcode logs:

2017-12-12 09:30:52.976644+0100 FCM registration token: <token>
2017-12-12 09:30:52.977 [warn][tid:main][RCTEventEmitter.m:54] Sending `messaging_token_refreshed` with no listeners registered.
2017-12-12 09:30:53.636 [info][tid:com.facebook.react.JavaScript] 'onTokenRefresh: listener:', [Function]

Environment

1. Application Target Platform:
   Both, currently only tested on iOS.

1. Development Operating System:
   macOS 10.13.1

1. Build Tools:
   Xcode 9.2

1. React Native version: 0.50.4

1. RNFirebase Version: 3.1.1

1. Firebase Module: messaging

[Frexuz]

Same here.

• Xcode 9.2
• RN 0.49.3
• Firebase 3.1.1
• Firebase/Core 4.7.0 pod

[chrisbianca]

Thanks for flagging this - we will address this as part of the FCM overhaul that we plan on doing for the next major release: https://github.com/invertase/react-native-firebase/issues/595

[hegelstad]

I still have this error.

"react": "^16.2.0",
"react-native": "^0.52.1",
"react-native-firebase": "^3.2.2",

[sibelius]

same error here

[hegelstad]

This should be in the documentation until its fixed.

Workaround that works pretty well, request current token manually at regular intervals such as app open.

[sibelius]

@hegelstad do u have an example of this?

[chrisbianca]

As stated above, this will be resolved as part of #595 which is currently well underway

[hegelstad]

@sibelius, considering firebase.messaging().getToken() is a quite cheap call, just call it regularly, it will always contain the latest token. The downside is the increased data usage, so dont update it too often.

[chrisbianca]

Good news, the long awaited alpha of our messaging and notifications overhaul is now available!!

Check out the release notes here: https://github.com/invertase/react-native-firebase/releases/tag/v4.0.0-alpha.1

If you have any comments and suggestions or want to report an issue, come find us on Discord

[apoterenko]

Seems like it not works. At the first time, a token is null

"version": "4.0.4"

  componentDidMount() {
    firebase.messaging().getToken().then((token) => {
      if (token) {
        this.setState({token: 'T2' + token})
      }
    });

    firebase.messaging().onTokenRefresh((token) => {
      if (token) {
        this.setState({token: 'T1' + token})
      }
    });
  }

On a next start, it works.. T2xsdgrw34324...

[gugat]

@chrisbianca which is the right way and place to call onTokenRefresh?,

In Android Studio's LogCat I see this message
D/RNFInstanceIdService: onTokenRefresh event received but it doesn't trigger the call to onTokenRefresh I put at componentDidMount().

As others have pointed out, it is not called. I am using version 4.0.6 with react native 0.55.3 .
For now, as @hegelstad mentions, calling firebase.messaging().getToken() regularly is the way to go.