集成Flutter AAR至Flutter项目遇引擎启动错误求助

报错Could not resolve main entrypoint function的核心原因是：你使用了宿主Flutter应用的bundle路径初始化AAR中Dart模块的入口点，而FlutterInjector.instance().flutterLoader().findAppBundlePath()指向的是宿主App的Flutter资源，并非你打包在AAR里的Dart模块资源。

1. 修正Dart入口点的路径获取 #

对于flutter build aar生成的Flutter模块AAR，其Dart产物路径需从AAR自身资源中获取，替换原有的入口点初始化代码：

// 替换原来的dartEntrypoint初始化逻辑
val flutterLoader = FlutterInjector.instance().flutterLoader()
// 获取AAR中Flutter模块的bundle路径，若你的模块入口文件不是main.dart，替换为对应文件名
val moduleBundlePath = flutterLoader.getBundlePathForAsset("main.dart")
val dartEntrypoint = DartExecutor.DartEntrypoint(moduleBundlePath, "german")

2. 确保自定义入口函数不被编译器移除 #

虽然你已添加@pragma('vm:entry-point')注解，但需确保构建AAR时该函数未被Dart编译器优化删除：

• 在Flutter模块的pubspec.yaml中添加配置，禁止不必要的代码摇树：

  flutter:
    build_args:
      - --no-tree-shake-icons
  

• 在Flutter模块的android/proguard-rules.pro中添加规则，保留入口函数及相关类：

  -keep class io.flutter.** { *; }
  -keep class io.flutter.plugins.** { *; }
  # 替换为你的Dart模块对应的包名，确保入口函数所在类不被混淆
  -keep class com.your.module.package.** { *; }
  

3. 等待引擎初始化完成后再调用MethodChannel #

直接在onCreate中调用invokeMethod可能因引擎未初始化完成失败，需监听引擎生命周期：

sdkEngine.addEngineLifecycleListener(object : FlutterEngine.EngineLifecycleListener {
    override fun onEngineCreated() {}
    override fun onEngineDestroyed() {}
    override fun onPreEngineRestart() {}
    override fun onEngineInitialized() {
        // 引擎初始化完成后再执行MethodChannel调用
        MethodChannel(sdkEngine.dartExecutor.binaryMessenger, "com.example/scan").invokeMethod("scan", null, object : MethodChannel.Result {
            override fun success(result: Any?) {
                println("poc SCAN called from Android")
            }

            override fun error(code: String, message: String?, details: Any?) {
                println("poc Received error: $code $message")
            }

            override fun notImplemented() {
                println("poc Method not implemented on Flutter side")
                throw NotImplementedError()
            }
        })
    }
})

4. 验证AAR依赖配置 #

确认app/build.gradle中的仓库路径指向flutter build aar生成的repo目录，且debug/release变体依赖对应正确的AAR包：

// 确保仓库路径正确指向本地生成的AAR仓库
repositories {
    maven {
        url '/Users/username/zdev/ios-sdk-bridge/build/host/outputs/repo'
    }
    maven {
        url "https://storage.googleapis.com/download.flutter.io"
    }
}

dependencies {
    debugImplementation 'com.trackbar.tracker_sdk_bridge:flutter_debug:1.0'
    releaseImplementation 'com.trackbar.tracker_sdk_bridge:flutter_release:1.0'
}

• 若在纯原生Android应用中集成Flutter AAR，需确保已完整配置Flutter依赖（如在settings.gradle中正确引入Flutter模块或maven仓库）。
• 避免同一进程中初始化多个Flutter引擎，防止资源冲突。

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