Closed djibarian closed 2 years ago
If this behavior is present only on Android, it's due Firebase's auto-initialization. By default, if there is connection to the internet the Firebase's SDK will generate a token and .registerRemoteNotificationsRegistered will be triggered.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
The issue has been closed for inactivity.
I've noticed that calling
Notifications.events().registerRemoteNotificationsRegistered(callback)
immediately fires the callback. Is this the expected behaviour?If so, it's a bit confusing, as I am delaying the call to the callback until
Notifications.registerRemoteNotifications()
as a result of the user being logged in to get the user's Id. But with the current behaviour I have to check inside the callback if the user's Id is available, which is not ideal.