Device token management in Firebase - Commands & Configuration

Introduction

Device token management helps you send notifications to specific devices by keeping track of their unique tokens. It solves the problem of targeting messages correctly to users' devices in Firebase Cloud Messaging.

When you want to send a notification to a specific user's phone or tablet.

When you need to update or remove a device token after the app is uninstalled or reinstalled.

When you want to manage multiple devices for one user and send notifications to all of them.

When you want to handle token refresh events to keep tokens valid for messaging.

When you want to store device tokens securely in your backend for sending targeted messages.

Commands

Log in to your Firebase account to access your projects and manage device tokens securely.

Terminal

firebase login

Expected Output

✔  Success! Logged in as [e-mail]

List all Firebase projects linked to your account to find the project where you want to manage device tokens.

Terminal

firebase projects:list

Expected Output

Project Display Name       Project ID           Project Number

my-app-project             my-app-project-id    123456789012

Deploy your Firebase Cloud Functions that handle device token registration and updates.

Terminal

firebase deploy --only functions

Expected Output

✔  Deploy complete!

Project Console: https://console.firebase.google.com/project/my-app-project/overview

→

--only functions - Deploy only the Cloud Functions part without affecting other Firebase services

View logs of your Cloud Functions to verify device token management functions are running correctly.

Terminal

firebase functions:log

Expected Output

2024-06-01T12:00:00.000Z myFunction: Device token saved for user123

2024-06-01T12:05:00.000Z myFunction: Device token refreshed for user456

Key Concept

If you remember nothing else from this pattern, remember: device tokens must be securely stored and updated to ensure notifications reach the right devices.

Common Mistakes

Not handling token refresh events in the app.

Tokens can expire or change, so old tokens become invalid and notifications won't be delivered.

Implement listeners in the app to detect token refresh and update the backend with the new token.

Storing device tokens insecurely or publicly.

Exposing tokens can allow unauthorized users to send fake notifications or spam.

Store tokens securely in your backend with proper authentication and access controls.

Not removing tokens when users uninstall the app.

Sending notifications to invalid tokens wastes resources and can cause errors.

Implement logic to detect uninstalls or invalid tokens and remove them from your database.

Summary

Use Firebase CLI commands to log in, list projects, deploy functions, and check logs for device token management.

Deploy Cloud Functions to handle saving, updating, and removing device tokens securely.

Always update tokens on refresh and remove invalid tokens to ensure notifications reach the correct devices.