Swift应用中Headless Flutter/Dart插件的MethodChannel实现问题

问题背景 #

尝试实现一个可从iOS函数调用的简单Headless Dart模块，目前Dart端所有打印日志均正常输出（无错误日志），但Swift模块中的isReady回调未打印日志。另外在call_dart_module()末尾添加无限循环后稳定性提升，想确认该问题是否与进程终止或无法处理回调有关，同时想知道使用Headless模块时MethodChannel是否有特定配置要求。

相关代码 #

AppDelegate.swift代码 #

import UIKit
import Flutter

@main
class AppDelegate: UIResponder, UIApplicationDelegate {

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        call_dart_module();
        // Override point for customization after application launch.
        return true
    }

    func application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions) -> UISceneConfiguration {
        return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
    }

    func application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>) {
    }
    
    func call_dart_module(){
        print("iOS part start");
        lazy var flutterEngine = FlutterEngine(name: "my flutter engine", project: nil,allowHeadlessExecution: true)
       
        flutterEngine.run();
        
        let methodChannel = FlutterMethodChannel(name: "com.test.shouldwork/ios", binaryMessenger: flutterEngine.binaryMessenger);
        
        methodChannel.setMethodCallHandler({
                 (call: FlutterMethodCall, result: @escaping FlutterResult) -> Void in
            if (call.method == "isReady") {
                print("isReady");
            }
        })
    }
}

Dart代码 #

main(){
    var platform = const MethodChannel('com.test.shouldwork/ios');
    print("start");
    WidgetsFlutterBinding.ensureInitialized();

    //platform.setMethodCallHandler(_receiveFromHost);
    try{
       platform.invokeMethod("isReady");
       print("worked");
    } catch (e){
      print('error');
    }
   
    print("end");
}

问题分析与解决 #

核心问题原因 #

1. FlutterEngine生命周期异常：call_dart_module()中用lazy var声明的flutterEngine是局部变量，方法执行完毕后会被系统立即释放，导致绑定的MethodChannel失去通信载体，无法接收Dart端的调用请求。
2. 进程终止风险：Headless模式下，Dart端main函数执行完成后，Flutter引擎默认会被销毁，此时iOS端的回调逻辑还没来得及处理。添加无限循环后，引擎进程被强制保持，回调能正常触发，直接验证了进程终止是问题的核心诱因之一。

解决方案 #

• 保留FlutterEngine实例：将flutterEngine提升为AppDelegate的成员变量，避免方法执行完毕后被释放：

  @main
  class AppDelegate: UIResponder, UIApplicationDelegate {
      // 声明为成员变量，延长生命周期
      private var flutterEngine: FlutterEngine?
  
      func call_dart_module(){
          print("iOS part start");
          flutterEngine = FlutterEngine(name: "my flutter engine", project: nil, allowHeadlessExecution: true)
          flutterEngine?.run();
          
          let methodChannel = FlutterMethodChannel(name: "com.test.shouldwork/ios", binaryMessenger: flutterEngine!.binaryMessenger);
          
          methodChannel.setMethodCallHandler({
                  (call: FlutterMethodCall, result: @escaping FlutterResult) -> Void in
              if (call.method == "isReady") {
                  print("isReady");
                  // 必须调用result返回结果，避免Dart端等待超时
                  result(nil)
              }
          })
      }
  }
  

• 维持引擎活跃状态：如果Dart端无需长期运行，可在调用MethodChannel后等待回调完成再结束逻辑；如果需要持续运行，可通过iOS后台任务机制或Dart Isolate保持进程活跃。
• 完善回调逻辑：iOS端的MethodCallHandler必须调用result方法返回结果，否则Dart端会触发超时错误，即使未捕获也会影响通信稳定性。

Headless模式下MethodChannel的注意事项 #

• 必须保证FlutterEngine实例的生命周期覆盖MethodChannel通信的全过程，避免局部变量导致的提前释放。
• allowHeadlessExecution: true是Headless模式的必要配置，但需注意引擎启动时机和资源释放逻辑。
• Dart端必须先初始化WidgetsFlutterBinding（当前代码已实现），否则MethodChannel无法正常工作。

内容的提问来源于stack exchange，提问作者aloys-c