Flutter Navigator场景下如何判断是否传递路由参数及解决空值类型转换报错

Hey there, let's fix that red screen error you're seeing! The problem comes down to how you're handling the route arguments in ProductPage: when you tap "Add Product", you aren't passing any arguments, so ModalRoute.of(context)!.settings.arguments is null—but you're forcing it to be a String with as String, which causes that "null is not a subtype of type String" crash.

You don't need to pass dummy parameters for the Add flow. Instead, adjust how you retrieve and check the arguments in ProductPage to handle both null and String cases safely. Here are two clean ways to do this:

Option 1: Check for Null and Type Safety #

Modify your ProductPage to first grab the arguments without an immediate cast, then validate them:

class ProductPage extends StatelessWidget {
  static const routname = 'productpage';
  
  @override
  Widget build(BuildContext context) {
    // Get arguments without forcing a non-null or String type
    final args = ModalRoute.of(context)?.settings.arguments;
    
    // Determine mode: Edit if args exists and is a String
    final isEditMode = args != null && args is String;
    
    return Scaffold(
      appBar: AppBar(title: const Text('Product management screen')),
      body: Text(isEditMode ? 'Edit Mode (ID: $args)' : 'Add Mode'),
    );
  }
}

Why this works: #

• Using ModalRoute.of(context)?.settings.arguments (with the nullable ? operator) avoids crashing if ModalRoute is ever null (a rare but safe guard).
• We first check if args is not null and is actually a String before treating it as an edit ID—this covers both your Add (null) and Edit (String ID) cases.
• You can even display the ID in Edit mode for extra clarity, like in the example above.

Option 2: Nullable Cast #

Another concise approach is to use a nullable cast (as String?), which lets Dart know the arguments could be a String or null:

class ProductPage extends StatelessWidget {
  static const routname = 'productpage';
  
  @override
  Widget build(BuildContext context) {
    // Cast arguments to nullable String (null if no args or wrong type)
    final productId = ModalRoute.of(context)?.settings.arguments as String?;
    
    return Scaffold(
      appBar: AppBar(title: const Text('Product management screen')),
      body: Text(productId != null ? 'Edit Mode (ID: $productId)' : 'Add Mode'),
    );
  }
}

Why this works: #

• as String? tells Dart we accept either a valid String or null. When you tap "Add Product", productId will be null instead of throwing a cast error.
• The null check for productId directly tells us which mode we're in.

Your original HomeScreen code doesn't need any changes—keep the "Add Product" button as is (no arguments) and the "Edit Product" button passing the ID. Both flows will now work without errors!

内容的提问来源于stack exchange，提问作者Irfan Ganatra