Sending messaging_token_refreshed with no listeners registered.

[chrisbianca]

Opening to track this outstanding issue.

This happens on iOS when the bridge is not properly initialised.
We need to add in a caching mechanism as happens with the initial notification.

[krozett]

Could you elaborate on this issue please? I am getting push notifications in the background but not the foreground, and this could be the cause.

[chrisbianca]

@krozett When the iOS app starts, it may receive a message token before the JS side of the app has been initialised. In this instance, the native iOS code tries to send it over the bridge and this triggers the warning. We just need to delay this from happening until the JS code is ready to receive the event.

This won't have anything to do with you receiving the notifications themselves.

[chrisbianca]

This is now fixed pending release of v4.0.3