Platform channels (MethodChannel) in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What is the output when calling a native method with MethodChannel?

Consider this Flutter code snippet that calls a native method named getBatteryLevel using MethodChannel. What will be the output shown in the Flutter app if the native side returns 85?

Flutter

final MethodChannel channel = MethodChannel('samples.flutter.dev/battery');

Future<void> getBatteryLevel() async {
  final int batteryLevel = await channel.invokeMethod('getBatteryLevel');
  print('Battery level is $batteryLevel%');
}

// Assume getBatteryLevel() is called and native returns 85

A Battery level is 85%

B Battery level is null%

C Battery level is 0%

D Error: Method not found

💡 Hint

Think about what the native side returns and how Flutter receives it.

The Flutter app calls the native method via MethodChannel. If the native side returns 85, Flutter receives it as an integer and prints 'Battery level is 85%'.

❓ lifecycle

intermediate

When should you set up the MethodChannel listener in Flutter?

In a Flutter app using MethodChannel to receive messages from native code, when is the best lifecycle moment to set up the setMethodCallHandler listener to avoid missing messages?

A Inside the <code>main()</code> function before runApp()

B Inside the <code>build()</code> method of a StatelessWidget

C Inside the <code>dispose()</code> method

D Inside the <code>initState()</code> method of a StatefulWidget

💡 Hint

Think about when the widget is first created and ready to handle messages.

Setting up the listener inside initState() ensures it is ready when the widget is active and avoids missing messages. build() can be called multiple times, dispose() is too late, and main() is before Flutter widgets exist.

📝 Syntax

advanced

What error does this Flutter MethodChannel code produce?

Examine this Flutter code snippet using MethodChannel. What error will it cause when run?

Flutter

final MethodChannel channel = MethodChannel('samples.flutter.dev/battery');

Future<void> getBatteryLevel() async {
  final int batteryLevel = await channel.invokeMethod('getBatteryLevel');
  print('Battery level is $batteryLevel%');
}

A SyntaxError due to missing semicolons

B No error, runs correctly

C Runtime error: Method not found

D TypeError: batteryLevel is null

💡 Hint

Check the punctuation carefully in Dart code.

Dart requires semicolons at the end of statements. Missing semicolons cause syntax errors.

❓ navigation

advanced

How to navigate after receiving a native message via MethodChannel?

You receive a message from native code via MethodChannel in Flutter. You want to navigate to a new screen named DetailsPage when the message arrives. Which code snippet correctly performs this navigation inside the setMethodCallHandler?

Flutter

channel.setMethodCallHandler((call) async {
  if (call.method == 'showDetails') {
    // Navigate to DetailsPage
  }
});

A All of the above are correct if context is available

B Navigator.of(context).push(MaterialPageRoute(builder: (_) => DetailsPage()));

C Navigator.pushNamed(context, '/details');

D Navigator.push(context, MaterialPageRoute(builder: (_) => DetailsPage()));

💡 Hint

Think about Flutter navigation methods and context availability.

Option B uses the correct syntax: `Navigator.of(context).push(...)`. Options B and C are invalid because `Navigator` does not have static `push` or `pushNamed` methods. Option B is incorrect. The key is having `BuildContext` accessible inside the handler.

🔧 Debug

expert

Why does Flutter not receive native messages via MethodChannel?

A developer sets up a MethodChannel in Flutter and native Android code to send messages. However, Flutter never receives the messages. Which is the most likely cause?

A Flutter does not have internet permission

B The native code uses a different thread to send messages

C The MethodChannel name strings do not match exactly between Flutter and native code

D The Flutter app is missing a MaterialApp widget

💡 Hint

Check the channel name carefully in both Flutter and native code.

MethodChannel communication depends on matching channel names exactly. If they differ, messages won't be received.

Practice

1. What is the main purpose of MethodChannel in Flutter?

easy

A. To manage app navigation

B. To communicate between Flutter and native platform code

C. To create UI widgets in Flutter

D. To handle Flutter animations

Solution

1. Step 1: Understand Flutter and native code interaction

   Flutter apps sometimes need to use features only available in native code like Android or iOS.

2. Step 2: Role of MethodChannel

   MethodChannel is the way Flutter sends messages to native code and gets results back.

3. Final Answer:

   To communicate between Flutter and native platform code -> Option B

4. Quick Check:

   MethodChannel = Flutter-native communication [OK]

Hint: MethodChannel connects Flutter with native code [OK]

Common Mistakes:

• Thinking MethodChannel creates UI widgets
• Confusing MethodChannel with navigation or animation
• Assuming MethodChannel runs only in Flutter without native code

2. Which of the following is the correct way to create a MethodChannel in Flutter?

easy

A. var channel = new MethodChannel();

B. MethodChannel channel = MethodChannel();

C. MethodChannel channel = MethodChannel('com.example.channel');

D. var channel = MethodChannel.create('channel');

Solution

1. Step 1: Check MethodChannel constructor usage

   The constructor requires a string name to identify the channel, e.g., 'com.example.channel'.

2. Step 2: Validate options

   MethodChannel channel = MethodChannel('com.example.channel'); correctly uses MethodChannel('com.example.channel'). Options A, C, and D are invalid syntax or missing required parameters.

3. Final Answer:

   MethodChannel channel = MethodChannel('com.example.channel'); -> Option C

4. Quick Check:

   MethodChannel needs a channel name string [OK]

Hint: MethodChannel constructor needs a channel name string [OK]

Common Mistakes:

• Omitting the channel name string
• Using 'new' keyword unnecessarily
• Calling non-existent create() method

3. Given this Flutter code snippet, what will be printed if the native side returns the string "Hello from native"?

final channel = MethodChannel('com.example.channel');
String message = await channel.invokeMethod('greet');
print(message);

medium

A. null

B. Empty string

C. An error message

D. "Hello from native"

Solution

1. Step 1: Understand invokeMethod behavior

   The invokeMethod sends a message to native code and waits for a response.

2. Step 2: Native returns "Hello from native" string

   The returned string is assigned to message and printed.

3. Final Answer:

   "Hello from native" -> Option D

4. Quick Check:

   invokeMethod returns native response string [OK]

Hint: invokeMethod returns native response awaited as result [OK]

Common Mistakes:

• Assuming invokeMethod returns null if native responds
• Expecting invokeMethod to print automatically
• Ignoring await causing Future object print

4. What is wrong with this Flutter code snippet for calling native code?

final channel = MethodChannel('com.example.channel');
channel.invokeMethod('getData');
print('Data received');

medium

A. invokeMethod is not awaited, so print runs before data arrives

B. MethodChannel name is invalid

C. invokeMethod requires a callback parameter

D. print statement syntax is incorrect

Solution

1. Step 1: Check asynchronous call usage

   invokeMethod returns a Future and should be awaited to get the result before proceeding.

2. Step 2: Analyze print timing

   Without await, print('Data received') runs immediately, before native response arrives.

3. Final Answer:

   invokeMethod is not awaited, so print runs before data arrives -> Option A

4. Quick Check:

   Always await invokeMethod for native response [OK]

Hint: Always await invokeMethod to get native result before next code [OK]

Common Mistakes:

• Not awaiting invokeMethod causing timing issues
• Thinking MethodChannel name is invalid without reason
• Expecting invokeMethod to take a callback parameter

5. You want to send a message from Flutter to native Android code to get battery level. Which steps are needed to implement this using MethodChannel? Choose the correct sequence.

hard

A. 1. Create MethodChannel in Flutter with a name
2. Call invokeMethod('getBatteryLevel')
3. In Android native code, set MethodCallHandler on same channel name
4. Handle 'getBatteryLevel' method and return battery level
5. Flutter receives battery level response

B. 1. Create MethodChannel in Flutter with a name
2. Directly access Android battery API from Flutter
3. No native code needed
4. Flutter gets battery level

C. 1. Create MethodChannel in Flutter
2. Call invokeMethod without method name
3. Android native code listens on different channel name
4. Return battery level

D. 1. Use Flutter plugin battery package
2. No need to write native code or MethodChannel
3. Flutter gets battery level

Solution

1. Step 1: Setup MethodChannel in Flutter

   Create a channel with a unique name to communicate with native code.

2. Step 2: Call invokeMethod with method name

   Flutter sends 'getBatteryLevel' request to native side.

3. Step 3: Setup native Android MethodCallHandler

   Native code listens on the same channel name and handles method calls.

4. Step 4: Native code returns battery level

   Native side gets battery info and sends it back.

5. Step 5: Flutter receives and uses battery level

   Flutter awaits response and uses the data.

6. Final Answer:

   1. Create MethodChannel in Flutter with a name 2. Call invokeMethod('getBatteryLevel') 3. In Android native code, set MethodCallHandler on same channel name 4. Handle 'getBatteryLevel' method and return battery level 5. Flutter receives battery level response -> Option A

7. Quick Check:

   Flutter-native communication needs matching channel and method handling [OK]

Hint: Match channel name and method handler on both sides [OK]

Common Mistakes:

• Skipping native code setup for MethodCallHandler
• Calling invokeMethod without method name
• Using different channel names on Flutter and native sides