FCM registration token colon not allowed about azure-notificationhubs-dotnet HOT 4 CLOSED

@marcobaldo no, it means you shouldn't use the FCM token as the installation ID. They are not the same thing. The installation ID can be any valid value. People typically use a GUID. It should be a value that you know and control.

The FCM token is not a value that you control and it contains characters that are not valid for use in the installation ID. The FCM token will change occasionally and unexpectedly.

When you create (or update) the installation you should set the PushChannel property to the value of the FCM token.

from azure-notificationhubs-dotnet.

@brannon that makes so much more sense. Thank you.

from azure-notificationhubs-dotnet.

This is by design. The token provided by FCM is not intended to be used as the installation ID. The token value can change over time, while the intention of the installation ID is to uniquely identify a particular app installation. The installation ID should be stable, while the FCM token should be specified as a property of the installation and updated frequently.

from azure-notificationhubs-dotnet.

@brannon does this mean that for fcm, we can only use registrations and not installations?

from azure-notificationhubs-dotnet.