Flutter升级至v0.2.11后出现类型不匹配运行时错误求助

Hey there, let's work through this runtime error you're hitting after upgrading to Flutter v0.2.11. This issue comes down to stricter type checking in newer Flutter releases—your code is passing a dynamically typed map where a Map<String, String> is explicitly expected.

What's Triggering the Error? #

Looking at your apiCall function, two key spots are causing the type mismatch:

1. The stringParams map is declared without explicit generic types, so it defaults to Map<dynamic, dynamic>. When you pass this to Uri.https, the method expects a Map<String, String> for query parameters.
2. The body parameter in http.post might be implicitly typed as Map<String, dynamic> if apiKey isn't guaranteed to be a String, which doesn't align with the method's requirement of Map<String, String> (or raw String).

Step-by-Step Fixes #

• Explicitly type stringParams: Declare it as Map<String, String> to ensure all keys and values are strings from the get-go.
• Guarantee apiKey is a String in the request body: If apiKey isn't already a String, convert it with toString(), or explicitly type it as a String in your variable declaration.
• Optional: Type the params input: Adding a generic type to the params parameter makes your code safer and eliminates implicit dynamic typing.

Modified Code Example #

Future apiCall([Map<String, dynamic> params = const {}]) async {
  loading = true;
  // Explicitly define stringParams as Map<String, String>
  Map<String, String> stringParams = {};
  params.forEach((k, v) => stringParams[k.toString()] = v.toString());
  
  Uri url = Uri.https(apiDomain, apiPath, stringParams);
  print(url);
  
  var result = await http.post(
    url,
    // Ensure apiKey is treated as a String
    body: {'apikey': apiKey.toString()}
  );
  
  loading = false;
  print(result.body);
  // Optional: Cast decoded result to a specific type for safer usage
  return json.decode(result.body) as Map<String, dynamic>;
}

Quick Extra Check #

If you still run into issues, verify that apiDomain and apiPath are both String values—any non-string values here could also introduce type inconsistencies. Flutter's newer versions enforce type safety more strictly, so explicit typing will help you avoid these runtime hiccups going forward.

内容的提问来源于stack exchange，提问作者Jeff Mikels