Is registerDeviceForRemoteMessages needed if auto-registration is not disabled?

[Awadi-R]

Hi,

We're seeing the following error for some users of our app, when calling messaging().getToken():

You must be registered for remote messages before calling getToken, see messaging().registerDeviceForRemoteMessages().

However, we do not have a firebase.json file that disables auto-registration (using the messaging_ios_auto_register_for_remote_messages parameter).

It's unclear to me whether all devices should call registerDeviceForRemoteMessages() on startup (as stated in the release notes here) or if that's only needed when auto-registration has been disabled (as implied by the console warning here).

I also wanted to verify, based on this other issue whether requesting permissions has anything to do with it. According to the Apple Docs, it seems that prompting for permissions is only needed to show user-facing notifications, and we're so we're not calling messaging().requestPermission() because we're interested in non-user-facing data messages with FCM. But I wanted to check anyway if that might be to blame for our failed FCM auto-registration.

Thank you!

[mikehardy]

We get an large amount of issue traffic, so I'm hesitant to remove any of the messages that help developers get things working, even if it means a few not-quite-necessary messages for users with different setups.

In this case, I think it never hurts to just call the API, double-calling it does nothing wrong, and then your log is clear

[ice-cap0]

Edit: removed what was a bug on our end. For some reason Push Notification capability was removed from Signing & Capabilities and we were getting the same error mentioned by op

[mikehardy]

Well, if there was a useful outcome, it was detection of that problem! That's pretty serious.
Note I think you need 14.12.0 if you are currently avoiding the use_frameworks stuff in v15 - 1c77741

[ice-cap0]

thx for the note @mikehardy you're everywhere! updating now