Flutter pushAndRemoveUntil使用异常：误移除Dashboard页面求助

Hey there, let's break down what's happening here and fix that back button issue!

Why Your Dashboard Is Getting Removed #

The pushAndRemoveUntil method works by pushing your new ReservationIntroPage and then removing every route in the stack until it finds a route that matches your predicate (ModalRoute.withName('/dashboard')). If pressing back closes the app entirely, that means the predicate didn't match your Dashboard route—so all previous routes (including Dashboard) were removed, leaving only the new ReservationIntroPage in the stack.

This could be happening for a couple of reasons tied to your onGenerateRoute setup:

• Your Dashboard route doesn't actually have the name /dashboard assigned to it in onGenerateRoute.
• The ModalRoute.withName predicate is failing because your Dashboard route isn't a subclass of ModalRoute (like using a custom route instead of MaterialPageRoute).
• There's a mismatch between the route name you're checking and the one registered for Dashboard.

How to Fix It #

Let's go through step-by-step solutions:

1. Verify Your Dashboard Route Name First

Double-check that your onGenerateRoute correctly assigns the /dashboard name to your Dashboard page, and uses a MaterialPageRoute (which is a ModalRoute subclass):

Route<dynamic> onGenerateRoute(RouteSettings settings) {
  switch (settings.name) {
    case '/dashboard':
      // Ensure this uses MaterialPageRoute
      return MaterialPageRoute(builder: (context) => Dashboard());
    case '/reservation-intro':
      return MaterialPageRoute(
        builder: (context) => ReservationIntroPage(
          sharedPreferences: settings.arguments as SharedPreferences,
        ),
      );
    // Add other routes here
    default:
      return MaterialPageRoute(builder: (context) => NotFoundPage());
  }
}

Also confirm your MaterialApp uses /dashboard as the initial route:

MaterialApp(
  initialRoute: '/dashboard',
  onGenerateRoute: onGenerateRoute,
  // ... other settings
);

2. Use a More Reliable Predicate

Instead of relying on ModalRoute.withName, use a custom predicate that directly checks the route's name. This avoids any issues with route type mismatches:

Navigator.pushAndRemoveUntil(
  context,
  MaterialPageRoute(
    builder: (context) => ReservationIntroPage(
      sharedPreferences: widget.sharedPreferences,
    ),
    // Optional: Assign a name to this new route for consistency
    settings: RouteSettings(name: '/reservation-intro'),
  ),
  // Keep routes until we hit the Dashboard
  (route) => route.settings.name == '/dashboard',
);

3. Debug the Route Stack (Optional but Helpful)

If you're still stuck, print the current route stack before and after navigation to see exactly what's happening:

// Before navigation
print('Current route stack: ${Navigator.of(context)}');

Navigator.pushAndRemoveUntil(/* ... */).then((_) {
  // After navigation
  print('Updated route stack: ${Navigator.of(context)}');
});

This will show you all routes in the stack, so you can confirm if Dashboard is present and has the correct name.

Bonus: Should You Push a New Page or Pop Back?

If you don't need a fresh instance of ReservationIntroPage (e.g., no new arguments to pass), you could instead pop back to the existing ReservationIntroPage while keeping Dashboard in the stack:

Navigator.popUntil(context, (route) => 
  route.settings.name == '/reservation-intro' || 
  route.settings.name == '/dashboard'
);

This removes all routes between the current screen and ReservationIntroPage without pushing a new instance.

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