Dart throws ConcurrentModificationError while looping over a list
Exception: Concurrent modification during iteration: Instance(length:17) of '_GrowableList'.Short answer
Dart throws this when a collection changes size while something iterates it. The usual culprits are a remove or add inside a for-in or forEach, and an await inside the loop that lets other code change the list. Iterate a copy, or use a single removeWhere call.
Fix it fast
1Find out which cause you have
Read the stack trace to find the loop, then look at every line inside it for add, remove, insert or clear on the same list.
grep -rn "\.remove(\|\.removeAt(\|\.add(\|\.insert(\|\.clear(" lib | head -402Match what you see, then jump to its fix
- 1
The trace points at a for-in loop or a forEach call, and its body calls remove or add on that listThe loop body changes the list it is readingFix - 2
The loop contains await, and the error shows up only sometimes, often after a tap or a network eventAn await in the loop lets other code change the listFix
- 1
What does the error look like?
Exception: Concurrent modification during iteration: Instance(length:17) of '_GrowableList'.ConcurrentModificationError
Cause 1 of 2
The loop body changes the list it is reading
1Check
Changing a list's length between iteration steps causes the error. Look for the list variable on both sides.
grep -n "for (.* in items)\|items.forEach" -A6 lib/cart.dart2Fix
Remove with one removeWhere call, or loop over a copy and change the original.
items.removeWhere((item) => item.isExpired);
for (final item in items.toList()) {
if (item.isExpired) items.remove(item);
}3Verify
Run the screen that failed and repeat the action.
flutter runConfirmed by api.dart.dev
Cause 2 of 2
An await in the loop lets other code change the list
1Check
An await inside the loop lets other code run between two steps. If that code adds to or removes from the list, its length changes between steps, which is what the error reports.
grep -n "await" lib/sync.dart2Fix
Take a snapshot before the loop and iterate over that.
final snapshot = List.of(queue);
for (final job in snapshot) {
await upload(job);
queue.remove(job);
}3Verify
Trigger the case that used to fail, for example adding items while the loop is running.
flutter runConfirmed by api.dart.dev
How do I stop it coming back?
- Never add to or remove from a list inside a loop over that same list.
- Use removeWhere for filtering in place.
- Copy the list with List.of or toList before an async loop.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
- SessionBirdAn omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.
Related fixes
Mobile apps
AudioCache has no play method after updating audioplayers
The method 'play' isn't defined for the type 'AudioCache'.
Since audioplayers 1.0, AudioCache only turns asset files into local files and caches them.
2 causes, each with a fixMobile apps
Flutter Bloc throws that emit was called after the event handler completed
emit was called after an event handler completed normally.
Each on<Event> handler gets its own Emitter, and it stops working the moment the handler's returned Future completes.
2 causes, each with a fixMobile apps
analysis_options.yaml: the URI it includes can't be found
include_file_not_found
The analyzer reports include_file_not_found when the file named after include: in analysis_options.yaml does not resolve.
2 causes, each with a fixMobile apps
Dart error: the body might complete normally and return null for a non-nullable type
body_might_complete_normally
Dart found a path through your function or callback that reaches the closing brace without a return.
3 causes, each with a fixMobile apps
Dart cannot turn a compact timestamp like 20201101153000 into a DateTime
FormatException: Invalid date format
DateTime.parse accepts a subset of ISO 8601, and a time part must be introduced by T or a space.
2 causes, each with a fixMobile apps
FormatException: Invalid radix-10 number when parsing a string to int
FormatException: Invalid radix-10 number
int.parse accepts only a whole-number literal.
3 causes, each with a fix