Bird
Raised Fist0
Firebasecloud~10 mins

Notification handling in background in Firebase - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to register the background message handler.

Firebase
import { getMessaging, onBackgroundMessage } from 'firebase/messaging/sw';

const messaging = getMessaging();
onBackgroundMessage(messaging, (payload) => {
  console.log('Received background message ', [1]);
});
Drag options to blanks, or click blank then click option'
Apayload
Bevent
Cmessage
Ddata
Attempts:
3 left
💡 Hint
Common Mistakes
Using an undefined variable name instead of the callback parameter.
Confusing event objects with payload data.
2fill in blank
medium

Complete the code to show a notification with title and body from the payload.

Firebase
self.registration.showNotification(payload.notification.[1], {
  body: payload.notification.body
});
Drag options to blanks, or click blank then click option'
Atitle
Bmessage
Cheader
Dtext
Attempts:
3 left
💡 Hint
Common Mistakes
Using incorrect property names like 'message' or 'header'.
Trying to access nested properties incorrectly.
3fill in blank
hard

Fix the error in the background message handler to correctly access notification data.

Firebase
onBackgroundMessage(messaging, (payload) => {
  const notificationTitle = payload.[1].title;
  const notificationOptions = {
    body: payload.notification.body
  };
  self.registration.showNotification(notificationTitle, notificationOptions);
});
Drag options to blanks, or click blank then click option'
Adata
Bpayload
Cmessage
Dnotification
Attempts:
3 left
💡 Hint
Common Mistakes
Accessing payload.data.title instead of payload.notification.title.
Using incorrect property names.
4fill in blank
hard

Fill both blanks to correctly extract title and body from the payload and show notification.

Firebase
const title = payload.[1].title;
const options = { body: payload.[2].body };
self.registration.showNotification(title, options);
Drag options to blanks, or click blank then click option'
Anotification
Bdata
Dmessage
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing data and notification properties.
Using different properties for title and body.
5fill in blank
hard

Fill all three blanks to handle background message, extract title and body, and show notification.

Firebase
onBackgroundMessage(messaging, ([1]) => {
  const title = [1].[2].title;
  const options = { body: [1].[2].body };
  self.registration.showNotification(title, options);
});
Drag options to blanks, or click blank then click option'
Apayload
Bnotification
Cdata
Devent
Attempts:
3 left
💡 Hint
Common Mistakes
Using different names for the callback parameter.
Confusing data with notification.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard