Dart says a value can't be returned because of the declared return type
return_of_invalid_typeShort answer
The analyzer reports return_of_invalid_type when a function returns a value that does not fit its declared return type. Either convert the value to the declared type, or change the declared type to match. In async code, the declared return type must be Future of the value type.
Fix it fast
1Find out which cause you have
Read the two types named in the message and the line it points to. The rest of this page is about which one of the two is wrong.
dart analyze2Match what you see, then jump to its fix
- 1
The function body uses async or await but the return type is int, String or a model classAn async function is declared with a plain typeFix - 2
No async keyword is involved, for example a function declared to return String that returns an intThe returned value has a different type than the signature promisesFix
- 1
What does the error look like?
return_of_invalid_typeA value of type can't be returned from method because it has a return type of
Cause 1 of 2
An async function is declared with a plain type
1Check
Look at the signature. A function marked async hands its value back inside a future.
grep -rnE "^\s*(int|String|bool|List<.*>) \w+\(.*\) async" lib2Fix
Dart's async guide says to wrap the declared return type in Future of the value's type, and the callers then await the result.
// before
String loadName() async { return 'Maaz'; }
// after
Future<String> loadName() async { return 'Maaz'; }
final name = await loadName();3Verify
Run the analyzer again; the error on that function is gone.
dart analyzeConfirmed by dart.dev
Cause 2 of 2
The returned value has a different type than the signature promises
1Check
Compare the declared type with the type of the expression after return.
dart analyze2Fix
Dart's own diagnostic page offers two fixes: replace the returned value with one of the right type, or change the return type to the type of the value.
// convert the value
String f() => 3.toString();
// or change the declared type
int f() => 3;3Verify
Run the analyzer; the diagnostic is no longer reported.
dart analyzeConfirmed by dart.dev
How do I stop it coming back?
- Write the return type first and let the analyzer check each return statement against it.
- Mark every async method's type as Future<T> or Future<void> in the same edit that adds async.
- Run dart analyze in CI so type mismatches cannot be merged.
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 throws ConcurrentModificationError while looping over a list
ConcurrentModificationError
Dart throws this when a collection changes size while something iterates it.
2 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 fix