You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Flutter driver should provide better error handling for malformed RPCs #172127
Today if you call a flutter driver extension, they assume the RPCs are well formed. Presumably, this is safe today because the expectation is all these calls are coming from actual flutter driver API calls.
I am trying to integrate the Dart MCP server with flutter driver (see dart-lang/ai#222), and inevitably the LLMs will create bad RPC calls into flutter driver.
It would be very helpful if the error messages were better so the LLM could figure out its mistake. Mostly commonly what I see today is just raw null assertion errors or "too many elements" errors.
Proposal
All flutter_driver RPC handlers should have explicit error handling instead of using ! and .single, so that it can provide nice errors about which arguments were malformed, missing, etc.
This is definitely valid @jakemac53, but it's unlikely we're going to have cycles to prioritize this on the tool side (I'm not even completely sure who owns package:flutter_driver these days).
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
jakemac53 commentedon Jul 14, 2025
Some example output today:
and
tirth-patel-nc commentedon Jul 15, 2025
thanks for the report. labelled as a new proposal for team's tracking.
bkonyi commentedon Jul 29, 2025
This is definitely valid @jakemac53, but it's unlikely we're going to have cycles to prioritize this on the tool side (I'm not even completely sure who owns
package:flutter_driverthese days).jakemac53 commentedon Jul 29, 2025
I might be willing to take it on - it should be pretty trivial and would greatly improve the LLM experience. I run into this constantly
Flutter driver deserialization (#172927)
github-actions commentedon Sep 11, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.Flutter driver deserialization (flutter#172927)
Flutter driver deserialization (flutter#172927)
Flutter driver deserialization (flutter#172927)
Flutter driver deserialization (flutter#172927)
Flutter driver deserialization (#172927)