Loading and error states in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Loading Indicator Visibility

What will be displayed on the screen when the isLoading variable is true in this Flutter widget?

Flutter

class LoadingWidget extends StatelessWidget {
  final bool isLoading;
  LoadingWidget({required this.isLoading});

  @override
  Widget build(BuildContext context) {
    return Center(
      child: isLoading ? CircularProgressIndicator() : Text('Content Loaded'),
    );
  }
}

A A spinning circular progress indicator is shown.

B A blank screen is shown.

C The text 'Content Loaded' is shown.

D An error message is shown.

💡 Hint

Check what widget is returned when isLoading is true.

When isLoading is true, the widget shows a CircularProgressIndicator, which is a spinning circle indicating loading.

❓ ui_behavior

intermediate

Error Message Display

Given this Flutter widget, what text will appear if hasError is true?

Flutter

class ErrorWidgetExample extends StatelessWidget {
  final bool hasError;
  ErrorWidgetExample({required this.hasError});

  @override
  Widget build(BuildContext context) {
    return Center(
      child: hasError ? Text('Failed to load data') : Text('Data loaded successfully'),
    );
  }
}

A Nothing is shown.

B The text 'Data loaded successfully' is shown.

C A loading spinner is shown.

D The text 'Failed to load data' is shown.

💡 Hint

Look at the condition that controls which text is shown.

When hasError is true, the widget shows the error message text.

❓ lifecycle

advanced

State Update After Async Load

In this Flutter stateful widget, what happens if setState is not called after data is loaded asynchronously?

Flutter

class DataLoader extends StatefulWidget {
  @override
  _DataLoaderState createState() => _DataLoaderState();
}

class _DataLoaderState extends State<DataLoader> {
  bool isLoading = true;
  String data = '';

  @override
  void initState() {
    super.initState();
    loadData();
  }

  Future<void> loadData() async {
    await Future.delayed(Duration(seconds: 2));
    data = 'Loaded Data';
    // Missing setState here
  }

  @override
  Widget build(BuildContext context) {
    return Center(
      child: isLoading ? CircularProgressIndicator() : Text(data),
    );
  }
}

A The loading spinner will never disappear and data will not show.

B The data text will appear immediately without loading spinner.

C The app will crash with an error.

D The loading spinner will disappear but data text will be empty.

💡 Hint

Think about what triggers the UI to update in Flutter stateful widgets.

Without calling setState, Flutter does not know the state changed, so the UI stays showing the loading spinner.

❓ navigation

advanced

Error Screen Navigation

Which code snippet correctly navigates to an error screen when an error occurs during data loading in Flutter?

Flutter

Future<void> loadData(BuildContext context) async {
  try {
    await fetchData();
  } catch (e) {
    // Navigate to error screen
  }
}

A Navigator.pushReplacement(context, MaterialPageRoute(builder: (_) => ErrorScreen()));

B Navigator.pop(context, MaterialPageRoute(builder: (_) => ErrorScreen()));

C Navigator.push(context, MaterialPageRoute(builder: (_) => ErrorScreen()));

D Navigator.pushNamed(context, '/error');

💡 Hint

Use navigation to add a new screen on top of the current one.

Using Navigator.push adds the error screen on top, showing it to the user.

🧠 Conceptual

expert

Best Practice for Loading and Error States

Which approach best improves user experience when handling loading and error states in a Flutter app?

A Show a blank screen until data loads, then show content or crash on error.

B Show a loading spinner during data fetch, then show content or an error message with retry option.

C Show content immediately and update silently without any loading or error indicators.

D Show an error message first, then load data in the background without user feedback.

💡 Hint

Think about clear communication and giving users control.

Showing a spinner during loading and an error message with retry improves clarity and user control.

Practice

1. What is the main purpose of showing a loading state in a Flutter app?

easy

A. To inform the user that data is being fetched or processed

B. To display an error message when something fails

C. To navigate to a new screen automatically

D. To permanently block user interaction

Solution

1. Step 1: Understand loading state purpose

   Loading states indicate to users that the app is busy fetching or processing data.

2. Step 2: Differentiate from error state

   Error states show problems, not progress. Loading states show progress.

3. Final Answer:

   To inform the user that data is being fetched or processed -> Option A

4. Quick Check:

   Loading state = show progress [OK]

Hint: Loading means waiting, not error or navigation [OK]

Common Mistakes:

• Confusing loading with error messages
• Thinking loading blocks app permanently
• Assuming loading triggers navigation

2. Which Flutter widget is commonly used to show a loading spinner?

easy

A. Text

B. ListView

C. CircularProgressIndicator

D. Container

Solution

1. Step 1: Identify loading spinner widget

   CircularProgressIndicator is the built-in widget for showing a spinner in Flutter.

2. Step 2: Exclude other widgets

   Text shows text, Container is a box, ListView shows lists, none show spinners.

3. Final Answer:

   CircularProgressIndicator -> Option C

4. Quick Check:

   Spinner widget = CircularProgressIndicator [OK]

Hint: Spinner = CircularProgressIndicator in Flutter [OK]

Common Mistakes:

• Using Text widget to show spinner
• Confusing Container with spinner
• Trying to use ListView for loading

3. What will the following Flutter code display when isLoading is true?

bool isLoading = true;

Widget build(BuildContext context) {
  if (isLoading) {
    return CircularProgressIndicator();
  } else {
    return Text('Data loaded');
  }
}

medium

A. A text saying 'Data loaded'

B. A runtime error

C. An empty screen

D. A circular loading spinner

Solution

1. Step 1: Check condition when isLoading is true

   The if condition is true, so CircularProgressIndicator() is returned.

2. Step 2: Understand widget output

   CircularProgressIndicator shows a spinner, not text or error.

3. Final Answer:

   A circular loading spinner -> Option D

4. Quick Check:

   isLoading true shows spinner [OK]

Hint: If isLoading true, show spinner widget [OK]

Common Mistakes:

• Assuming text shows when loading is true
• Expecting empty screen instead of spinner
• Thinking code causes error

4. Identify the error in this Flutter snippet for showing error or loading states:

bool hasError = false;
bool isLoading = true;

Widget build(BuildContext context) {
  if (hasError) {
    return Text('Error occurred');
  } else if (isLoading) {
    CircularProgressIndicator();
  } else {
    return Text('Content loaded');
  }
}

medium

A. Missing return before CircularProgressIndicator()

B. Wrong boolean variable names

C. Text widget cannot show error messages

D. Using else if instead of if

Solution

1. Step 1: Check all return statements

   hasError branch returns Text, else branch returns Text, but isLoading branch calls CircularProgressIndicator without return.

2. Step 2: Understand Flutter build method needs return

   Every branch must return a widget; missing return causes error.

3. Final Answer:

   Missing return before CircularProgressIndicator() -> Option A

4. Quick Check:

   All branches must return widgets [OK]

Hint: Always return widgets in build method branches [OK]

Common Mistakes:

• Forgetting return keyword before widgets
• Confusing variable names
• Thinking else if is wrong here

5. You want to show a loading spinner, then an error message if loading fails, or content if successful. Which Flutter widget structure correctly handles this with booleans isLoading and hasError?

hard

A. if (isLoading) return CircularProgressIndicator(); else if (hasError) return Text('Error'); else return Text('Content');

B. if (hasError) return Text('Error'); else if (isLoading) return CircularProgressIndicator(); else return Text('Content');

C. if (isLoading && hasError) return CircularProgressIndicator(); else return Text('Content');

D. if (hasError) return CircularProgressIndicator(); else if (isLoading) return Text('Loading'); else return Text('Content');

Solution

1. Step 1: Prioritize error over loading

   If there is an error, show error message first before loading or content.

2. Step 2: Show loading only if no error and loading is true

   Then show spinner if loading is true and no error.

3. Step 3: Show content if no error and not loading

   Finally, show content when no error and loading is false.

4. Final Answer:

   if (hasError) return Text('Error'); else if (isLoading) return CircularProgressIndicator(); else return Text('Content'); -> Option B

5. Quick Check:

   Error first, then loading, then content [OK]

Hint: Show error before loading, loading before content [OK]

Common Mistakes:

• Showing loading before error
• Combining error and loading in one condition
• Using wrong widgets for states