Flutter Mobile Development · Lesson

Error Handling in Async

Implement robust error handling strategies for asynchronous operations, ensuring your app gracefully manages network failures and exceptions.

Error Handling in Async is a free Flutter Mobile Development lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Flutter Mobile Development learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Handling Unpredictable Async Errors

Asynchronous operations, like fetching data from the internet or reading files, are inherently unpredictable. They might succeed, fail, or even time out.

Robust error handling is crucial to prevent your app from crashing and to provide a smooth user experience. It allows you to gracefully manage these failures.

`try-catch` for Async Operations

The familiar try-catch block in Dart is your primary tool for handling exceptions in asynchronous code. When an await expression throws an error, it can be caught by an enclosing try-catch block.

try: Contains the code that might throw an exception.
catch: Catches and handles the exception if one occurs.
on: (Optional) Catches specific types of exceptions.

Catching a Simulated Error

Let's see try-catch in action. This example simulates a network error by throwing an Exception within an async function. Notice how catch handles it.

import 'dart:async';

Future<String> fetchData() async {
  await Future.delayed(Duration(seconds: 1));
  // Simulate a network error
  throw Exception("Failed to fetch data!");
  return "Data received"; // This line won't be reached
}

void main() async {
  print("Starting data fetch...");
  try {
    String data = await fetchData();
    print("Success: $data");
  } catch (e) {
    print("Error caught: $e");
  } finally {
    print("Fetch attempt complete.");
  }
}

Handling Specific Exception Types

Sometimes, you want to handle different types of errors in different ways. The on keyword allows you to catch specific exception types, making your error handling more precise.

For example, you might handle a SocketException (network issue) differently from a generic Exception.

Targeted Error Handling

Here, we define two types of errors: a custom NetworkException and a generic Exception. The on clause lets us provide specific handling for each.

import 'dart:async';

class NetworkException implements Exception {
  final String message;
  NetworkException(this.message);
  @override
  String toString() => 'NetworkException: $message';
}

Future<void> performNetworkCall(bool shouldFailNetwork) async {
  await Future.delayed(Duration(milliseconds: 500));
  if (shouldFailNetwork) {
    throw NetworkException("No internet connection!");
  } else {
    throw Exception("An unknown error occurred.");
  }
}

void main() async {
  print("Attempt 1: Simulate network failure");
  try {
    await performNetworkCall(true);
  } on NetworkException catch (e) {
    print("Caught specific network error: ${e.message}");
  } catch (e) {
    print("Caught generic error: $e");
  }

  print("\nAttempt 2: Simulate unknown error");
  try {
    await performNetworkCall(false);
  } on NetworkException catch (e) {
    print("Caught specific network error: ${e.message}");
  } catch (e) {
    print("Caught generic error: $e");
  }
}

Ensuring Cleanup with `finally`

The finally block is an optional part of a try-catch statement. Code inside this block will always execute, regardless of whether an exception was thrown or caught.

It's perfect for cleanup operations, like closing a file stream or dismissing a loading indicator, ensuring resources are properly managed.

Alternative: `Future.catchError`

While try-catch works well with async/await, you can also handle errors directly on a Future object using its .catchError() method. This is often used when chaining Futures or when not using await immediately.

It takes a function that will be called if the Future completes with an error.

Handling Errors with `catchError`

Here's how .catchError() can be used. Notice that the error is handled as part of the Future's completion chain, without needing an async function or await for the error handling itself.

import 'dart:async';

Future<String> getUserData() {
  return Future.delayed(Duration(seconds: 1)).then((_) {
    throw Exception("User data not found!");
    return "User data"; // Unreachable
  });
}

void main() {
  print("Fetching user data...");
  getUserData().then((data) {
    print("Success: $data");
  }).catchError((error) {
    print("Error with .catchError(): $error");
  }).whenComplete(() {
    print("User data fetch completed.");
  });
}

Good Practices for Error Handling

Effective error handling makes your app robust and user-friendly:

Log errors: Use a logging framework to record errors for debugging.
Provide feedback: Inform the user about what went wrong (e.g., "Network unavailable").
Retry mechanism: For transient network issues, consider offering a retry option.
Avoid empty catch blocks: Always handle or re-throw errors, don't just swallow them.

Async Error Handling Check

Consider the following Dart code snippet. Which statements about its error handling are true?

import 'dart:async';

Future<String> riskyOperation() async {
  await Future.delayed(Duration(milliseconds: 100));
  if (DateTime.now().second % 2 == 0) {
    throw FormatException("Invalid data format!");
  }
  return "Data processed.";
}

void main() async {
  try {
    String result = await riskyOperation();
    print("Result: $result");
  } on FormatException catch (e) {
    print("Specific error: ${e.message}");
  } catch (e) {
    print("Generic error: $e");
  } finally {
    print("Operation finished.");
  }
}

Recap: Mastering Async Errors

In this lesson, we explored how to handle errors in asynchronous Dart and Flutter applications. You learned:

The importance of robust error handling.
Using try-catch with async/await.
Catching specific exceptions with on.
Ensuring cleanup with finally.
An alternative: Future.catchError().
Best practices for building resilient apps.

Proper error handling is key to creating stable and user-friendly mobile experiences!

Frequently asked questions

Is the “Error Handling in Async” lesson free?

Yes — the full text of “Error Handling in Async” is free to read here on the web, and the Flutter Mobile Development course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Flutter Mobile Development course, upgrade to CoddyKit PRO.

What will I learn in “Error Handling in Async”?

Implement robust error handling strategies for asynchronous operations, ensuring your app gracefully manages network failures and exceptions. You practise Flutter Mobile Development with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Flutter Mobile Development?

No prior experience is required. Flutter Mobile Development on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Error Handling in Async” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Flutter Mobile Development lesson?

Yes. Every Flutter Mobile Development lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Flutter Mobile Development