Flutter Isolate中能否使用插件？VideoCompress报错咨询

• 原本可正常使用VideoCompress插件，将视频处理逻辑迁移至Isolate后触发如下错误：

Cannot set the method call handler before the binary messenger has been initialized. This happens when you call setMethodCallHandler() before the WidgetsFlutterBinding has been initialized. You can fix this by either calling WidgetsFlutterBinding.ensureInitialized() before this or by passing a custom BinaryMessenger instance to MethodChannel().

• 疑问：除VideoCompress外，Flutter插件是否可在Isolate中使用？

相关业务代码：

late Subscription _subscription;

// === Compressing
try {
  isolateSwitchToState(RecordingState.compressingVideo);

  // == Subscribe to progress
  _subscription = VideoCompress.compressProgress$.subscribe((progress) {
    debugPrint('progress: $progress');
    _send2main?.send(progress);
  });

  final videoDurationInSeconds = (videoMediaInfo.duration! / 1000).floor();
  final trimDurationInSec =
      min(purchasedDurationInSeconds, videoDurationInSeconds);

  finalMediaInfo = await VideoCompress.compressVideo(videoLocalPath,
      startTime: 0,
      // Possibly truncate the video to the purchased time extension: but it cannot exceed the initial duration, hence the min
      duration: videoDurationInSeconds - trimDurationInSec,
      quality: //VideoQuality.DefaultQuality // 58MiB
          //VideoQuality.Res640x480Quality  // 17MiB
          VideoQuality.Res960x540Quality // 34MiB
      //VideoQuality.Res1280x720Quality // 58MiB
      //VideoQuality.Res1920x1080Quality // 127MiB
      //VideoQuality.HighestQuality,
      );

  isolateSwitchToState(RecordingState.videoCompressed);

  // ==Now uploading
  if (finalMediaInfo == null || finalMediaInfo.file == null) {
    isolateSwitchToErrorState(
        i18n_The_compressed_video_file_or_file_info_is_null.i18n);
    return;
  }
} catch (e) {
  isolateSwitchToErrorState(
      i18n_While_compressing_to_the_video_file_s.i18n.fill([e.toString()]));
  return;
} finally {
  // == Unsuscribe from progression
  _subscription.unsubscribe();
}

[更新]错误来自MethodChannel的setMethodCallHandler方法断言：

/// Sets a callback for receiving method calls on this channel.
///
/// The given callback will replace the currently registered callback for this
/// channel, if any. To remove the handler, pass null as the
/// `handler` argument.
///
/// If the future returned by the handler completes with a result, that value
/// is sent back to the platform plugin caller wrapped in a success envelope
/// as defined by the [codec] of this channel. If the future completes with
/// a [PlatformException], the fields of that exception will be used to
/// populate an error envelope which is sent back instead. If the future
/// completes with a [MissingPluginException], an empty reply is sent
/// similarly to what happens if no method call handler has been set.
/// Any other exception results in an error envelope being sent.
void setMethodCallHandler(Future<dynamic> Function(MethodCall call)? handler) {
  assert(
    _binaryMessenger != null || BindingBase.debugBindingType() != null,
    'Cannot set the method call handler before the binary messenger has been initialized. '
    'This happens when you call setMethodCallHandler() before the WidgetsFlutterBinding '
    'has been initialized. You can fix this by either calling WidgetsFlutterBinding.ensureInitialized() '
    'before this or by passing a custom BinaryMessenger instance to MethodChannel().',
  );

具体触发位置为VideoCompress插件compress_mixin.dart中的代码：

class CompressMixin {
  final compressProgress$ = ObservableBuilder<double>();
  final _channel = const MethodChannel('video_compress');

  @protected
  void initProcessCallback() {
    _channel.setMethodCallHandler(_progressCallback);  // <<===== 错误触发点
  }

  MethodChannel get channel => _channel;

  bool _isCompressing = false;

  bool get isCompressing => _isCompressing;

  @protected
  void setProcessingStatus(bool status) {
    _isCompressing = status;
  }

  Future<void> _progressCallback(MethodCall call) async {
    switch (call.method) {
      case 'updateProgress':
        final progress = double.tryParse(call.arguments.toString());
        if (progress != null) compressProgress$.next(progress);
        break;
    }
  }
}

为什么Isolate中会触发该错误？ #

Isolate是独立的执行线程，默认不会自动初始化Flutter的Binding（包括WidgetsFlutterBinding）。而MethodChannel依赖BinaryMessenger实现与原生平台的通信，BinaryMessenger是在Binding初始化过程中创建的。

VideoCompress插件的CompressMixin中，initProcessCallback方法直接调用_channel.setMethodCallHandler，此时Isolate内的Binding未初始化，因此触发断言错误。

Flutter插件能否在Isolate中使用？ #

分两种场景：

• 纯Dart实现的插件：完全可以在Isolate中使用，无需依赖Flutter Binding，例如数据处理类插件。
• 依赖MethodChannel与原生交互的插件：可以在Isolate中使用，但需满足以下任一条件：
  1. 在Isolate中提前初始化Binding：调用ServicesBinding.ensureInitialized()（比WidgetsFlutterBinding更轻量，适合非UI场景）或WidgetsFlutterBinding.ensureInitialized()
  2. 给MethodChannel传入自定义BinaryMessenger实例（需借助IsolateNameServer或自定义消息传递机制，实现复杂度较高）

当前问题的修复方案 #

在Isolate的入口函数开头，先初始化轻量的ServicesBinding：

void isolateEntryPoint(SendPort sendPort) async {
  // 初始化ServicesBinding，满足MethodChannel通信需求
  ServicesBinding.ensureInitialized();
  
  // 后续视频压缩逻辑（即你原有业务代码）
  late Subscription _subscription;
  try {
    // ...你的原有代码
  } catch(e) {
    // ...错误处理逻辑
  }
}

注意：Isolate无法直接更新UI，进度回调需通过SendPort传递到主Isolate处理，你的代码中_send2main?.send(progress)的实现是正确的。

内容的提问来源于stack exchange，提问作者Stéphane de Luca