Unnecessary widget rebuilds when navigating between pages in Riverpod 3.0

[ricardosc12]

Description

After migrating from Riverpod 2.x to 3.0, I'm experiencing excessive widget rebuilds when navigating between pages. Every time I navigate to a new page, all previous pages in the navigation stack that extend ConsumerWidget are being rebuilt, even when they don't actively use any providers.

This behavior seems related to the new provider pause/resume mechanism in 3.0.

Expected Behavior (Riverpod 2.x)

• Navigate to Page1 → Only Page1 builds
• Navigate from Page1 to Page2 → Only Page2 builds
• Pop back from Page2 to Page1 → No rebuilds

Current Behavior (Riverpod 3.0)

• Navigate to Page1 → Page1 builds (correct)
• Navigate from Page1 to Page2 → Both Page1 AND Page2 build
• Pop back from Page2 to Page1 → Page1 builds again

This causes 3+ unnecessary rebuilds in my application just for simple navigation.

Example

class Page1 extends ConsumerWidget {
  const Page1({super.key});

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    print("[Widget Build] Page1");
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: Column(
          children: [
            Text("PAGE1"),
            ElevatedButton(
              onPressed: () {
                Navigator.of(context, rootNavigator: true).push(
                  PageRouteBuilder(
                    pageBuilder: (_, _, _) => const Page2(),
                    transitionDuration: Duration.zero,
                    reverseTransitionDuration: Duration.zero,
                  ),
                );
              },
              child: Text("Go to Page2"),
            ),
          ],
        ),
      ),
    );
  }
}

class Page2 extends ConsumerWidget {
  const Page2({super.key});

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    print("[Widget Build] Page2");
    return Scaffold(
      appBar: AppBar(),
      body: Center(child: Text("PAGE2")),
    );
  }
}

Output

// Navigate to Page1
[Widget Build] Page1  ✓ Expected

// Navigate from Page1 to Page2
[Widget Build] Page1  ✗ Unexpected rebuild!
[Widget Build] Page2  ✓ Expected

// Pop back to Page1
[Widget Build] Page1  ✗ Unexpected rebuild!

Important Notes

The widgets don't even need to call ref.watch() or ref.read() to trigger this behavior
Simply extending ConsumerWidget is enough to cause the rebuilds

Question

Is this the intended behavior in Riverpod 3.0? If so, is there a way to opt-out of this for navigation scenarios where we want to preserve the previous behavior?

The automatic provider pause/resume feature is great, but rebuilding every ConsumerWidget in the stack seems excessive.

[rrousselGit]

This should've been fixed in the latest 3.2.0 version