Chapters
Chapters

Chapters

Hide chapters

Dart Apprentice: Beyond the Basics

First Edition · Flutter · Dart 2.18 · VS Code 1.71

Before You Begin

Section 0: 6 chapters
Show chapters Hide chapters

Dart Apprentice: Beyond the Basics

Section 1: 15 chapters
Show chapters Hide chapters

10. Error Handling
Written by Jonathan Sande

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

It’s natural to only code the happy path as you begin to work on a project.

  • “This text input will always be a valid email address.”
  • “The internet is always connected.”
  • “That function’s return value is always a positive integer.”

Until it isn’t.

When a baker makes a mistake, cookies get burned. When an author makes a mistake, words get mispelled. Eaters will swallow and readers overlook, but code doesn’t forgive. Maybe you noticed misspelled was “mispelled” in the previous sentence. Or maybe you missed it. We all make mistakes, but when a programmer makes one, the whole app crashes. That’s the nature of a programmer’s work. The purpose of this chapter is to teach you how to crash a little less.

Errors and Exceptions in Dart

The creators of Dart had such confidence you and your users would make mistakes that they built error handling right into the language. Before you learn how to handle errors, though, you get to make them!

How to Crash an App

You have many ways to cause your application to give up all hope of survival and quit. Open a new project and try out a few of them.

Dividing by Zero

One way to crash is to divide by zero. You learned in elementary school that you can’t do that.

No Such Method

In the past, you often got a NoSuchMethodError when you forgot to handle null values. Because the Null class doesn’t have many methods, almost anything you tried to do with null caused this crash.

Format Exception

Another way to crash your app is to try and decode a “JSON” string that isn’t actually in JSON format.

Reading Stack Traces

The sections above only gave you part of the error messages. You probably noticed that the full message was much longer and a lot of it looked like unintelligible gibberish. The unintelligible part is called a stack trace:

Vgavx xqibe
Ksobp blowo

jowgroocPyqaa zetgmaanPsa wutkriehAwi miil
Yisn xxuww

Mkenx twawi
Zlezj pwawi

Debugging

It’s not always obvious from the stack trace where the bug in your code is. VS Code has good debugging tools to help you out in this situation.

Writing Some Buggy Code

Replace your project file with the following code:

Adding a Breakpoint

Click the margin to the left of line 2. This will add a red dot:

Zxeojwearl ak lafe 3
Sbiicxausc es kora 8

Running in Debug Mode

Now, start your app in debug mode. Like before, there are a few ways to do that:

Stepping Over the Code Line by Line

VS Code pauses execution at line 2. Then, a floating button bar pops up with various debugging options. If you hover your mouse over each button, you can see what it does. The most important ones for now are the two on the left:

Bos itg Guwac qafef: Tekeipbep
Gim oyz Wofam wetic: Kozaekyow

Watching Expressions

When you tire of stepping one line at a time through the for loop, add a breakpoint to line 6: final letter = characters[index];.

Idyicb u Reqyd ebbyeydiek
Uyruhq a Lijql ochzavhieq

Fixing the Bug

When the app finally crashes, what’s the value of index?

Handling Exceptions

The bug in the last section was an actual error in the logic of the code. There was no way to handle that except to track down the bug and fix it.

Catching Exceptions

As you saw earlier, one source of these exceptions is invalid JSON. When connected to the internet, you can’t control what comes to you from the outside world. Invalid JSON doesn’t happen very often, but you should write code to deal with it when you get it.

Handling Specific Exceptions

Using a catch block will catch every exception that happens in the try block.

Handling Multiple Exceptions

When there’s more than one potential exception that could occur, you can use multiple on blocks to target them.

The Finally Block

There’s also a finally block you can add to your try-catch structure. The code in that block runs both if the try block is successful and if the catch or on block catches an exception.

Writing Custom Exceptions

You should use the standard exceptions whenever you can, but you can also define your own exceptions when appropriate.

Defining the Exceptions

First, create the following Exception class for passwords that are too short:

Throwing Exceptions

Now, add the following validation function below main:

Handling Custom Exceptions

Now that you have all the exceptions defined and the validation logic set up, you’re ready to use them. Replace the contents of main with the following code:

Challenges

Before moving on, here are some challenges to test your knowledge of error handling. It’s best if you try to solve them yourself, but solutions are available with the supplementary materials for this book if you get stuck.

Challenge 1: Double the Fun

Here’s a list of strings. Try to parse each of them with double.parse. Handle any format exceptions that occur.

Challenge 2: Five Digits, No More, No Less

  • Create a custom exception named InvalidPostalCode.
  • Validate that a postal code is five digits.
  • If it isn’t, throw the exception.

Key Points

  • An error is something that crashes your app.
  • An exception is a known situation you must plan for and handle.
  • Not handling an exception is an error.
  • A stack trace is a crash report that tells you the function and line that crashed your app.
  • VS Code debugging tools allow you to set breakpoints and execute your code one line at a time.
  • try/catch blocks are one way to handle exceptions.
  • It’s better to handle specific exceptions with the on keyword rather than blindly handling all exceptions with catch.
  • If you have a logic error in your app, don’t “handle” it with catch. Let your app crash and then fix the bug.
  • Add a finally block to try-catch if you need to clean up resources.
  • You can create custom exceptions that implement Exception.

Where to Go From Here?

It’s a good thing when your app crashes while developing it. That’s a signal of something you need to fix. But when your app crashes for your users after you’ve published it, that’s not such a good thing. Some people might email you when they find a bug. Others might leave a negative review online, but most users won’t tell you about crashes or bugs. For that reason, you might consider using a third-party crash reporting library in your app. It’ll collect crash reports in a central location. Analyzing those reports will help you find and fix bugs you wouldn’t otherwise know about.

9. Enhanced Enums
11. Concurrency
Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2026 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now