Flutter多环境集成测试报错：No requestData Extension registered问题求助

Let's break down what's causing this issue and how to fix it step by step.

What's Going Wrong? #

The core error No requestData Extension registered happens when the integrationDriver (in your test_driver/integration_test.dart) can't properly communicate with the IntegrationTestWidgetsFlutterBinding in your integration test file. Looking at your setup, the most likely culprit is a conflicting command-line parameter in how you're running the test.

Your command includes both --target=integration_test/app_test.dart (which points to your integration test) and -t lib/main_prod.dart (which points to your flavor-specific main entry). This confuses the flutter drive tool—it can't properly link the integration test logic to your app instance, leading to the extension registration failure.

Step-by-Step Fixes #

1. Fix the Test Run Command #

Remove the redundant -t lib/main_prod.dart parameter. Your flavor configuration should already be set up to load lib/main_prod.dart automatically when using --flavor prod. Here's the corrected command:

flutter drive \
 --driver=test_driver/integration_test.dart \
 --target=integration_test/app_test.dart \
 --flavor prod

If your flavor setup isn't automatically loading the correct main file, double-check your Android build.gradle (or iOS Info.plist) configuration to ensure the prod flavor maps to lib/main_prod.dart. For Android, your app/build.gradle should have something like:

flavorDimensions "environment"
productFlavors {
    prod {
        dimension "environment"
        applicationIdSuffix ".prod"
        // Ensure the correct main entry is linked
        sourceSets {
            main.dart.srcDirs += 'src/prod/dart'
        }
    }
}

2. Verify Integration Test Binding Initialization #

Make sure the integration test binding is initialized before any other code in your app_test.dart. While your current code looks correct, you can explicitly add the base Flutter binding first to avoid race conditions (especially if your main_prod.dart has early initialization logic like Firebase):

import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';
import 'package:flutter/material.dart';

void main() async {
  // Initialize base binding first
  WidgetsFlutterBinding.ensureInitialized();
  // Then initialize integration test binding
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();

  // If your app requires async initialization (like Firebase), wait for it here
  // await Firebase.initializeApp();

  testWidgets("failing test example", (WidgetTester tester) async {
    expect(2 + 2, equals(5));
  });
}

3. Check Dependencies and Flutter Version #

• Ensure your pubspec.yaml has the correct dev dependencies:

  dev_dependencies:
    flutter_test:
      sdk: flutter
    integration_test:
      sdk: flutter
  

• Run flutter pub get to sync dependencies.
• Try upgrading Flutter to the latest stable version (or downgrading to a known stable version if you're on a beta/dev channel) — some older versions had bugs with integration tests + flavors.

4. Isolate the Issue #

To confirm the flavor is the problem, run the integration test without the flavor flag first:

flutter drive --driver=test_driver/integration_test.dart --target=integration_test/app_test.dart

If this works, the issue is definitely tied to your flavor configuration. Double-check that all flavor-specific setup (like environment variables, app IDs, or initialization logic) doesn't interfere with the integration test binding.

Note on the VM Service Connection #

Don't worry about the VMServiceFlutterDriver: Connecting to http://127.0.0.1:... log — this is normal! Flutter uses the VM Service to communicate between your local machine and the device/emulator for integration tests, regardless of whether you're targeting Web, Android, or iOS.

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