How to Handle FCM Tokens for Multiple Accounts on a Single Device?

FCM Token Handling: One Device, Multiple Accounts

Firebase Cloud Messaging (FCM) tokens are generated for each instance of an app on a device, not for specific accounts. This can lead to confusion when handling user accounts within an app.

Database Storage of FCM Tokens

To send notifications to specific users, you may consider storing their FCM tokens in a database. However, when a user logs out and creates a new account using the same device, two rows (and tokens) will be present in the database for the same device.

Handling Token Changes

When a user switches accounts within the app, the FCM token for the device remains unchanged. This token represents the app instance on the device, regardless of the current user.

Database Updates

To avoid duplicate tokens, you should update the database as follows when a user logs out:

• Remove the mapping of the old token to the previous user.
• Add a new mapping of the same token to the new user.

Additional Considerations

• Uninstalling and reinstalling the app will generate a new token for the device.
• The Firebase Admin SDK can be used to send notifications using the device-specific token, ensuring that notifications are received even when the user changes accounts.

The above is the detailed content of How to Handle FCM Tokens for Multiple Accounts on a Single Device?. For more information, please follow other related articles on the PHP Chinese website!