Device token management in Firebase - Step-by-Step Execution

Process Flow - Device token management

App starts

↓

Request device token

↓

Receive token from Firebase

↓

Store token in database

↓

Use token to send notifications

↓

Token refresh event?

Yes→Get new token

↓

Update token in database

↓

End

The app requests a device token from Firebase, stores it, uses it for notifications, and updates it when refreshed.

Execution Sample

Firebase

firebase.messaging().getToken()
  .then(token => {
    saveTokenToDatabase(token);
  });

This code gets the device token from Firebase and saves it to the database.

Process Table

Step	Action	Firebase Response	Database Action	Result
1	App requests device token	Token requested	No action yet	Waiting for token
2	Firebase returns token	Token: abc123xyz	No action yet	Token received
3	Save token to database	N/A	Store token abc123xyz	Token stored
4	Send notification using token	N/A	Use token abc123xyz	Notification sent
5	Token refresh event occurs	New token requested	No action yet	Waiting for new token
6	Firebase returns new token	Token: def456uvw	No action yet	New token received
7	Update token in database	N/A	Replace old token with def456uvw	Token updated
8	No further refresh	N/A	No action	Process ends

💡 No token refresh event, process ends

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	After Step 7	Final
deviceToken	null	abc123xyz	abc123xyz	def456uvw	def456uvw	def456uvw
databaseToken	null	null	abc123xyz	abc123xyz	def456uvw	def456uvw

Key Moments - 2 Insights

Why do we need to update the token in the database after a refresh?

Because the token changes (see Step 6 and 7 in execution_table), and the database must have the current token to send notifications correctly.

What happens if the app does not request a new token after refresh?

Notifications will fail because the old token becomes invalid (refer to Step 5 and 6 where a new token is needed).

Visual Quiz - 3 Questions

Look at the execution_table, what is the device token after Step 3?

A null

B abc123xyz

C def456uvw

D Token not received yet

💡 Hint

Check the 'deviceToken' value after Step 3 in variable_tracker.

At which step does the token get updated in the database?

A Step 7

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Database Action' column in execution_table for token update.

If the token refresh event never occurs, what happens to the token in the database?

A It changes automatically

B It gets deleted

C It stays the same

D It causes an error

💡 Hint

Refer to the exit_note and final variable values in variable_tracker.

Concept Snapshot

Device token management in Firebase:
- Request token with getToken()
- Store token in database
- Use token to send notifications
- Listen for token refresh
- Update database with new token
- Keep tokens current for reliable messaging

Full Transcript

Device token management in Firebase involves the app requesting a unique token from Firebase Messaging. This token identifies the device for sending notifications. Once received, the token is saved in a database. The app uses this token to send notifications to the device. When Firebase refreshes the token, the app must get the new token and update it in the database to keep notifications working. If the token is not updated, notifications will fail. This process ensures reliable delivery of messages to the device.

Practice

1. What is the main purpose of a device token in Firebase Cloud Messaging?

easy

A. To store user passwords securely

B. To manage database access permissions

C. To track user location in real-time

D. To uniquely identify a device for sending notifications

Solution

1. Step 1: Understand device token role

   A device token is a unique identifier assigned to each device by Firebase to target messages.

2. Step 2: Match purpose with options

   Only To uniquely identify a device for sending notifications correctly describes the token's role in sending notifications to a specific device.

3. Final Answer:

   To uniquely identify a device for sending notifications -> Option D

4. Quick Check:

   Device token = unique device ID for messaging [OK]

Hint: Device tokens identify devices for messaging [OK]

Common Mistakes:

• Confusing tokens with passwords
• Thinking tokens track location
• Assuming tokens manage database access

2. Which Firebase method is used to delete a device token?

easy

A. firebase.messaging().clearToken()

B. firebase.messaging().removeToken()

C. firebase.messaging().deleteToken()

D. firebase.messaging().revokeToken()

Solution

1. Step 1: Recall Firebase token deletion method

   The correct method to delete a device token is deleteToken().

2. Step 2: Compare options with correct method

   Only firebase.messaging().deleteToken() matches the exact method name deleteToken().

3. Final Answer:

   firebase.messaging().deleteToken() -> Option C

4. Quick Check:

   Delete token method = deleteToken() [OK]

Hint: Delete tokens with deleteToken() method [OK]

Common Mistakes:

• Using removeToken() which does not exist
• Confusing clearToken() with deleteToken()
• Using revokeToken() which is invalid

3. Consider this code snippet:

const messaging = firebase.messaging();
const token = await messaging.getToken();
console.log(token);

What will be the output of console.log(token)?

medium

A. A unique string representing the device token

B. An error because getToken() requires parameters

C. Undefined because getToken() is not asynchronous

D. A boolean indicating token availability

Solution

1. Step 1: Understand getToken() behavior

   The getToken() method asynchronously returns a unique device token string.

2. Step 2: Analyze code output

   Since await is used, token holds the string token, so console.log prints that string.

3. Final Answer:

   A unique string representing the device token -> Option A

4. Quick Check:

   getToken() returns token string [OK]

Hint: getToken() returns a unique token string asynchronously [OK]

Common Mistakes:

• Thinking getToken() returns boolean
• Assuming getToken() needs parameters
• Ignoring async/await usage

4. You wrote this code to delete a device token:

firebase.messaging().deleteToken;

Why does this code fail to delete the token?

medium

A. deleteToken requires a token parameter which is missing

B. deleteToken is missing parentheses to call the function

C. deleteToken is not a valid Firebase method

D. deleteToken must be called on firebase.auth() instead

Solution

1. Step 1: Check method invocation syntax

   The code references deleteToken without parentheses, so the function is not called.

2. Step 2: Understand function call requirements

   To execute the function, parentheses () are required even if no parameters are passed.

3. Final Answer:

   deleteToken is missing parentheses to call the function -> Option B

4. Quick Check:

   Function calls need () to execute [OK]

Hint: Always use () to call functions like deleteToken() [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Assuming deleteToken needs parameters
• Calling deleteToken on wrong Firebase service

5. You want to send a notification only to devices of a specific user. Which is the best practice for managing device tokens in Firebase?

hard

A. Store each user's device tokens in a database linked to their user ID

B. Use a single global token for all users to simplify messaging

C. Delete tokens immediately after sending a notification

D. Generate new tokens manually for each notification

Solution

1. Step 1: Understand targeted messaging needs

   To send notifications to specific users, you must know their device tokens.

2. Step 2: Choose token management strategy

   Storing tokens linked to user IDs in a database allows targeted, reliable messaging.

3. Final Answer:

   Store each user's device tokens in a database linked to their user ID -> Option A

4. Quick Check:

   Link tokens to users for targeted notifications [OK]

Hint: Link tokens to user IDs in database for targeted messages [OK]

Common Mistakes:

• Using one token for all users
• Deleting tokens too soon
• Manually generating tokens instead of Firebase