Notification handling in background in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What happens when a Firebase Cloud Messaging (FCM) notification is received while the app is in the background?

The notification is automatically displayed in the device's notification tray without opening the app. The app can process data messages silently if configured.

beginner

What is the difference between notification messages and data messages in Firebase Cloud Messaging?

Notification messages are handled by the system and shown in the notification tray automatically, especially when the app is in the background. Data messages are delivered to the app for custom handling, even in the background if configured.

intermediate

How can you handle data messages in the background using Firebase on Android?

Implement a FirebaseMessagingService and override the onMessageReceived method. For background handling, ensure the message contains only data payload and the app has proper permissions and setup.

intermediate

Why is it important to keep background notification handling efficient and quick?

Because the system limits background processing time to save battery and resources. Long tasks may be killed or delayed, so handle notifications quickly and defer heavy work to foreground or scheduled jobs.

beginner

What role does the 'click_action' field play in background notifications?

It defines which app screen or activity opens when the user taps the notification from the tray, improving user experience by directing them to relevant content.

What type of Firebase message is automatically displayed by the system when the app is in the background?

A Token refresh message

B Data message

C Silent push

D Notification message

Notification messages are shown automatically by the system when the app is in the background.

Which Firebase service method should you override to handle messages in the background on Android?

A onMessageReceived

B onCreate

C onStartCommand

D onNotificationReceived

The onMessageReceived method in FirebaseMessagingService handles incoming messages.

What must a data message NOT include to ensure it is handled in the background by the app?

A Notification payload

B Data payload

C Click action

D Sound

Including a notification payload causes the system to handle the message automatically, bypassing app background processing.

Why should background notification handling be quick and efficient?

A To increase app size

B To avoid battery drain and system killing the process

C To delay user interaction

D To reduce network usage

Systems limit background work to save battery; slow handling risks termination.

What does the 'click_action' field in a notification do?

A Changes notification sound

B Sets notification priority

C Specifies which app screen opens on tap

D Defines message expiration

It directs the app to open a specific screen when the notification is tapped.

Explain how Firebase handles notifications when the app is in the background and how you can customize this behavior.

Think about the difference between notification and data messages and how the app reacts.

Describe best practices for managing background notification handling to ensure good user experience and system compliance.

Consider battery and resource constraints on mobile devices.

Practice

1. What is the main purpose of using onBackgroundMessage in Firebase Cloud Messaging?

easy

A. To authenticate users before sending notifications

B. To send messages from the client to the server

C. To handle notifications when the app is not open or in the background

D. To delete old notifications from the device

Solution

1. Step 1: Understand the role of onBackgroundMessage

   This function is designed to catch messages when the app is not active or open.

2. Step 2: Compare with other options

   Sending messages, authentication, or deleting notifications are unrelated to background message handling.

3. Final Answer:

   To handle notifications when the app is not open or in the background -> Option C

4. Quick Check:

   Background message handling = To handle notifications when the app is not open or in the background [OK]

Hint: Remember: background means app closed or hidden [OK]

Common Mistakes:

• Confusing sending messages with receiving them
• Thinking it manages user authentication
• Assuming it deletes notifications automatically

2. Which of the following is the correct way to import and use onBackgroundMessage in a Firebase service worker?

easy

A. import { onBackgroundMessage } from 'firebase/messaging/sw'; onBackgroundMessage(handler);

B. import { onBackgroundMessage } from 'firebase/messaging/sw'; onBackgroundMessage(messaging, handler);

C. import { onBackgroundMessage } from 'firebase/messaging'; messaging.onBackgroundMessage(handler);

D. import { onBackgroundMessage } from 'firebase/messaging'; onBackgroundMessage(messaging, handler);

Solution

1. Step 1: Identify correct import path

   The correct import for service worker usage is from 'firebase/messaging/sw'.

2. Step 2: Use correct function signature

   onBackgroundMessage requires only the handler function as argument (no messaging instance needed).

3. Final Answer:

   import { onBackgroundMessage } from 'firebase/messaging/sw'; onBackgroundMessage(handler); -> Option A

4. Quick Check:

   Correct import and call signature = import { onBackgroundMessage } from 'firebase/messaging/sw'; onBackgroundMessage(handler); [OK]

Hint: Remember: import from 'firebase/messaging/sw' and pass handler only [OK]

Common Mistakes:

• Importing from wrong path like 'firebase/messaging'
• Passing messaging instance to onBackgroundMessage
• Using messaging.onBackgroundMessage(handler)

3. Given this service worker code snippet, what will happen when a background message arrives?

import { onBackgroundMessage } from 'firebase/messaging/sw';
import { messaging } from './firebase-config';

onBackgroundMessage((payload) => {
  console.log('Received background message ', payload);
  self.registration.showNotification(payload.notification.title, {
    body: payload.notification.body
  });
});

medium

A. Only the message payload is logged, no notification is shown

B. The notification shows but the payload is not logged

C. An error occurs because showNotification is not a valid method

D. The message payload is logged and a notification with title and body is shown

Solution

1. Step 1: Analyze the callback function

   The callback logs the payload and calls showNotification with title and body from the payload.

2. Step 2: Confirm method validity

   self.registration.showNotification is the correct way to show notifications in service workers.

3. Final Answer:

   The message payload is logged and a notification with title and body is shown -> Option D

4. Quick Check:

   Payload logged + notification shown = The message payload is logged and a notification with title and body is shown [OK]

Hint: Check if both console.log and showNotification are called [OK]

Common Mistakes:

• Thinking showNotification is invalid in service workers
• Assuming logging disables notification
• Ignoring the payload content usage

4. You wrote this service worker code but notifications do not appear when the app is in background:

import { onBackgroundMessage } from 'firebase/messaging';
import { messaging } from './firebase-config';

onBackgroundMessage((payload) => {
  self.registration.showNotification(payload.notification.title, {
    body: payload.notification.body
  });
});

What is the main issue?

medium

A. Using self.registration.showNotification instead of Notification.show

B. Wrong import path for onBackgroundMessage ('firebase/messaging' instead of 'firebase/messaging/sw')

C. Not importing messaging from Firebase

D. Payload does not contain notification object

Solution

1. Step 1: Check onBackgroundMessage usage

   The import path is wrong for service worker; must be from 'firebase/messaging/sw'.

2. Step 2: Verify notification method and imports

   self.registration.showNotification is correct and messaging is imported but not needed.

3. Final Answer:

   Wrong import path for onBackgroundMessage ('firebase/messaging' instead of 'firebase/messaging/sw') -> Option B

4. Quick Check:

   Service worker import path = Wrong import path for onBackgroundMessage ('firebase/messaging' instead of 'firebase/messaging/sw') [OK]

Hint: Remember: import from 'firebase/messaging/sw' [OK]

Common Mistakes:

• Using wrong import path for onBackgroundMessage
• Confusing notification API names
• Assuming payload structure is always wrong

5. You want to ensure your Firebase app shows a notification with a custom icon and vibrates when a background message arrives. Which code snippet correctly adds these features inside onBackgroundMessage?

hard

A. onBackgroundMessage((payload) => { self.registration.showNotification(payload.notification.title, { body: payload.notification.body, icon: '/icon.png', vibrate: [100, 50, 100] }); });

B. onBackgroundMessage((payload) => { self.showNotification(payload.notification.title, { body: payload.notification.body, icon: '/icon.png', vibrate: [100, 50, 100] }); });

C. onBackgroundMessage((payload) => { Notification.show(payload.notification.title, { body: payload.notification.body, icon: '/icon.png', vibrate: [100, 50, 100] }); });

D. onBackgroundMessage((payload) => { self.registration.showNotification(payload.title, { body: payload.body, icon: '/icon.png', vibrate: [100, 50, 100] }); });

Solution

1. Step 1: Use correct notification method and parameters

   self.registration.showNotification is correct. The notification title and body come from payload.notification.

2. Step 2: Add icon and vibrate options properly

   Options icon and vibrate are correctly included in the options object.

3. Final Answer:

   onBackgroundMessage((payload) => { self.registration.showNotification(payload.notification.title, { body: payload.notification.body, icon: '/icon.png', vibrate: [100, 50, 100] }); }); -> Option A

4. Quick Check:

   Correct method, payload fields, and options = onBackgroundMessage((payload) => { self.registration.showNotification(payload.notification.title, { body: payload.notification.body, icon: '/icon.png', vibrate: [100, 50, 100] }); }); [OK]

Hint: Use self.registration.showNotification with full payload.notification fields [OK]

Common Mistakes:

• Using wrong notification method like self.showNotification
• Accessing payload.title instead of payload.notification.title
• Omitting icon or vibrate options