Notifications (local) in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when this Flutter local notification code runs?

Consider this Flutter code snippet that schedules a local notification:

await flutterLocalNotificationsPlugin.zonedSchedule(
  0,
  'Reminder',
  'Time to drink water!',
  tz.TZDateTime.now(tz.local).add(const Duration(seconds: 5)),
  const NotificationDetails(
    android: AndroidNotificationDetails('channelId', 'channelName'),
  ),
  androidAllowWhileIdle: true,
  uiLocalNotificationDateInterpretation: UILocalNotificationDateInterpretation.absoluteTime,
);

What will the user experience?

Flutter

await flutterLocalNotificationsPlugin.zonedSchedule(
  0,
  'Reminder',
  'Time to drink water!',
  tz.TZDateTime.now(tz.local).add(const Duration(seconds: 5)),
  const NotificationDetails(
    android: AndroidNotificationDetails('channelId', 'channelName'),
  ),
  androidAllowWhileIdle: true,
  uiLocalNotificationDateInterpretation: UILocalNotificationDateInterpretation.absoluteTime,
);

A A notification titled 'Reminder' with message 'Time to drink water!' appears after 5 seconds.

B The notification appears immediately without delay.

C The notification never appears because the scheduling method is incorrect.

D The app crashes due to missing permission handling.

💡 Hint

Look at the add(const Duration(seconds: 5)) part in the scheduled time.

The code schedules a notification to appear 5 seconds from now. The zonedSchedule method uses the local timezone and delay specified. So the notification will show after 5 seconds with the given title and message.

❓ lifecycle

intermediate

What happens if you schedule a local notification without initializing the plugin?

In Flutter, if you try to schedule a local notification without calling initialize() on FlutterLocalNotificationsPlugin, what will happen?

A The app will throw an exception at runtime.

B The notification will not appear but no error is thrown.

C The notification will be scheduled and shown normally.

D The app will crash immediately on startup.

💡 Hint

Think about what initialize() does for the plugin.

The initialize() method sets up platform-specific settings and callbacks. Without it, scheduling notifications will cause runtime exceptions because the plugin is not ready.

📝 Syntax

advanced

Which option correctly requests notification permissions on iOS in Flutter?

Which code snippet correctly requests notification permissions on iOS using flutter_local_notifications?

Flutter

final bool result = await flutterLocalNotificationsPlugin
  .resolvePlatformSpecificImplementation<IOSFlutterLocalNotificationsPlugin>()
  ?.requestPermissions(alert: true, badge: true, sound: true) ?? false;

A await flutterLocalNotificationsPlugin.requestPermissions(alert: true, badge: true, sound: true);

B await flutterLocalNotificationsPlugin.requestIOSPermissions(alert: true, badge: true, sound: true);

C await flutterLocalNotificationsPlugin.initialize(requestPermissions: true);

D await flutterLocalNotificationsPlugin.resolvePlatformSpecificImplementation<IOSFlutterLocalNotificationsPlugin>()?.requestPermissions(alert: true, badge: true, sound: true) ?? false;

💡 Hint

Look for the platform-specific implementation method.

On iOS, permissions must be requested via the platform-specific implementation. Option D correctly calls resolvePlatformSpecificImplementation<IOSFlutterLocalNotificationsPlugin>() and then requestPermissions().

❓ navigation

advanced

What happens when a user taps a local notification with this setup?

Given this Flutter notification initialization code:

await flutterLocalNotificationsPlugin.initialize(
  InitializationSettings(
    android: AndroidInitializationSettings('@mipmap/ic_launcher'),
    iOS: IOSInitializationSettings(),
  ),
  onDidReceiveNotificationResponse: (NotificationResponse response) {
    Navigator.of(context).pushNamed('/details');
  },
);

What happens when the user taps the notification?

A The app navigates to the '/details' screen.

B The app crashes due to missing context.

C The notification is dismissed but no navigation occurs.

D Nothing happens because Navigator cannot be used here.

💡 Hint

Consider where context comes from in the callback.

The onDidReceiveNotificationResponse callback does not provide a BuildContext, so using Navigator.of(context) here causes a runtime error because context is undefined.

🧠 Conceptual

expert

Why is timezone setup important for scheduling local notifications in Flutter?

In Flutter local notifications, why must you configure timezone data (e.g., using timezone package) before scheduling notifications with zonedSchedule?

A To enable notifications to show on Android only.

B To reduce battery usage by the notification plugin.

C To ensure notifications appear at the correct local time even if the device timezone changes.

D To allow notifications to include images and sounds.

💡 Hint

Think about what happens if the device timezone changes after scheduling.

Using timezone-aware scheduling ensures notifications trigger at the correct local time even if the user travels or changes device timezone. Without it, notifications may appear at wrong times.

Practice

1. What is the main purpose of local notifications in a Flutter app?

easy

A. To alert users even when the app is closed or in the background

B. To send messages to a server

C. To update the app's UI instantly

D. To change app theme colors automatically

Solution

1. Step 1: Understand local notifications

   Local notifications are alerts shown to users even if the app is not open or running in the background.

2. Step 2: Compare options

   Options B, C, and D describe other app features unrelated to local notifications.

3. Final Answer:

   To alert users even when the app is closed or in the background -> Option A

4. Quick Check:

   Local notifications alert users outside app use = A [OK]

Hint: Local notifications work when app is not active [OK]

Common Mistakes:

• Confusing local notifications with server messages
• Thinking notifications only work when app is open
• Mixing UI updates with notification purpose

2. Which Flutter plugin is commonly used to show local notifications?

easy

A. firebase_messaging

B. flutter_local_notifications

C. provider

D. http

Solution

1. Step 1: Identify notification plugins

   The plugin flutter_local_notifications is designed for local notifications in Flutter apps.

2. Step 2: Eliminate unrelated plugins

   http is for network calls, provider for state management, firebase_messaging for push notifications, not local.

3. Final Answer:

   flutter_local_notifications -> Option B

4. Quick Check:

   Local notifications plugin = flutter_local_notifications [OK]

Hint: Local notifications use flutter_local_notifications plugin [OK]

Common Mistakes:

• Choosing firebase_messaging which is for push, not local
• Confusing state management plugins with notification plugins
• Selecting network plugins by mistake

3. What will happen if you call show() on a local notification without initializing the plugin first?

medium

A. The notification will show normally

B. The notification will show only on Android devices

C. The notification will be delayed by 5 seconds

D. The app will crash or throw an error

Solution

1. Step 1: Understand plugin initialization

   Local notification plugins require initialization before use to set up channels and permissions.

2. Step 2: Consequence of missing initialization

   Calling show() without initialization causes runtime errors or crashes because the plugin is not ready.

3. Final Answer:

   The app will crash or throw an error -> Option D

4. Quick Check:

   Uninitialized plugin causes error/crash = B [OK]

Hint: Always initialize plugin before showing notifications [OK]

Common Mistakes:

• Assuming notifications show without initialization
• Thinking notifications delay automatically
• Believing platform-specific behavior without init

4. Given this code snippet, what is the error?

final FlutterLocalNotificationsPlugin flutterLocalNotificationsPlugin = FlutterLocalNotificationsPlugin();

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  // Missing initialization here
  await flutterLocalNotificationsPlugin.show(
    0,
    'Hello',
    'Welcome to Flutter',
    NotificationDetails(
      android: AndroidNotificationDetails('channelId', 'channelName')
    )
  );
}

medium

A. WidgetsFlutterBinding.ensureInitialized() is unnecessary

B. NotificationDetails is not imported

C. Missing call to initialize() before show()

D. Notification ID cannot be zero

Solution

1. Step 1: Check plugin initialization

   The code calls show() without calling initialize() on flutterLocalNotificationsPlugin first.

2. Step 2: Understand consequences

   Without initialize(), the plugin is not ready, causing errors when showing notifications.

3. Final Answer:

   Missing call to initialize() before show() -> Option C

4. Quick Check:

   Initialize plugin before show() = C [OK]

Hint: Always initialize plugin before calling show() [OK]

Common Mistakes:

• Ignoring the need to initialize plugin
• Thinking zero ID is invalid
• Assuming ensureInitialized() replaces plugin init

5. You want to create a local notification channel with high importance and priority on Android. Which code snippet correctly sets this up?

hard

A. AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high)

B. AndroidNotificationDetails('channelId', 'channelName', importance: Importance.low, priority: Priority.min)

C. AndroidNotificationDetails('channelId', 'channelName', importance: Importance.defaultImportance, priority: Priority.defaultPriority)

D. AndroidNotificationDetails('channelId', 'channelName')

Solution

1. Step 1: Understand importance and priority

   High importance and priority make notifications more visible and urgent on Android.

2. Step 2: Check code options

   AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high) sets importance and priority to high, matching the requirement. Others set low, default, or omit these settings.

3. Final Answer:

   AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high) -> Option A

4. Quick Check:

   High importance and priority = AndroidNotificationDetails('channelId', 'channelName', importance: Importance.high, priority: Priority.high) [OK]

Hint: Use Importance.high and Priority.high for urgent notifications [OK]

Common Mistakes:

• Leaving importance and priority at default
• Using low importance for urgent alerts
• Omitting priority setting