Device token management in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Firebase Cloud Messaging handle device tokens when a user reinstalls the app?

When a user uninstalls and then reinstalls your app, what happens to the device token used for push notifications?

A A new device token is generated after reinstalling the app.

B The device token remains the same as before the uninstall.

C The old token is reused only if the user logs in with the same account.

D The device token is deleted permanently and cannot be regenerated.

💡 Hint

Think about how Firebase ensures messages reach the correct device after app reinstall.

Firebase generates a new device token after the app is reinstalled to ensure secure and accurate message delivery.

❓ security

intermediate

What is the best practice to secure device tokens in your backend?

Which method best protects device tokens stored on your server to prevent unauthorized access?

A Store device tokens in plain text in a public database.

B Encrypt device tokens before storing them and restrict database access.

C Send device tokens only over unsecured HTTP connections.

D Share device tokens openly with third-party services without restrictions.

💡 Hint

Consider how sensitive data should be handled to avoid leaks.

Encrypting device tokens and restricting access helps protect user privacy and prevents misuse of tokens.

❓ Architecture

advanced

Designing a scalable system for device token updates

You have millions of users whose device tokens can change frequently. Which architecture best handles real-time token updates efficiently?

A Implement a distributed cache layer with asynchronous token update propagation.

B Use a single centralized database with synchronous writes for all token updates.

C Store tokens only on the client side and never update the server.

D Manually update tokens once a month via batch processing.

💡 Hint

Think about how to reduce latency and avoid bottlenecks in large-scale systems.

A distributed cache with asynchronous updates reduces load on the database and improves scalability for frequent token changes.

❓ Configuration

advanced

Firebase Cloud Messaging token refresh handling

Which Firebase method should you implement to handle device token refresh events correctly in your app?

Firebase

firebase.messaging().onTokenRefresh(callback)

A Delete the old token from Firebase console when a token refresh occurs.

B Ignore token refresh events; tokens never change after initial generation.

C Manually generate new tokens on the client without Firebase methods.

D Use firebase.messaging().onTokenRefresh(callback) to update the token on your server.

💡 Hint

Firebase provides a built-in way to detect token changes.

Using onTokenRefresh ensures your app updates the backend with the latest token to maintain message delivery.

✅ Best Practice

expert

Handling invalid device tokens in Firebase Cloud Messaging

When sending push notifications, some device tokens become invalid. What is the best practice to handle these invalid tokens?

A Keep sending notifications to all tokens regardless of errors.

B Manually reset tokens on the client device without server involvement.

C Remove tokens from your database when Firebase returns a 'NotRegistered' error.

D Ignore errors and retry sending notifications indefinitely.

💡 Hint

Consider how to keep your token list clean and efficient.

Removing tokens flagged as 'NotRegistered' prevents wasted resources and improves notification delivery success.

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