Flutter踩坑之 Could not find io.flutter.....

本文解决了一个在使用Android Studio打开Flutter项目并尝试构建时遇到的常见错误。错误信息显示无法解析多个依赖项,如flutter_embedding_debug和不同架构的调试版本。解决方法是在build.gradle文件中添加一个新的Maven仓库URL,指向Flutter的官方下载站点。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

用AS打开Flutter项目Android模块,然后build,结果报错如下:

Could not resolve all files for configuration ':app:debugCompileClasspath'.
> Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/flutter_embedding_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
> Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/arm64_v8a_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/arm64_v8a_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:arm64_v8a_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/arm64_v8a_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/arm64_v8a_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
> Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
> Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
  Required by:
      project :app
   > Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_64_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_64_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.
   > Could not resolve io.flutter:x86_64_debug:1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.
      > Could not parse POM http://download.flutter.io/io/flutter/x86_64_debug/1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94/x86_64_debug-1.0.0-e7f9ef6aa0b9040102d1b3c9a6ae934df746ef94.pom
         > Already seen doctype.

解决办法:

Android项目的build.gradle 

allprojects {
    repositories {
        ......
       //添加这一行
        maven { url "https://storage.googleapis.com/download.flutter.io" }
    }
}

重新build,完成

参考地址:https://github.com/flutter/flutter/issues/39729

<think>好的,我现在需要帮助用户解决在构建Flutter项目时遇到的依赖项找不到的问题,具体是关于com.arthenica:mobile-ffmpeg-full-gpl:4.4.LTS的缺失。首先,我得先理解用户的问题。用户提到了使用flutter_ffmpeg 0.4.2,并且遇到了依赖缺失的错误。根据用户提供的引用内容,尤其是引用[1]和[2],看起来ffmpeg-kit现在被推荐作为替代方案,取代了之前的MobileFFmpeg、flutter_ffmpeg等库。 首先,我应该检查用户当前的依赖配置是否正确。用户可能还在使用旧版的flutter_ffmpeg,而这个库已经被弃用,导致无法找到对应的依赖项。根据引用[1],ffmpeg_kit_flutter的LTS版本是5.1.0,可能需要用户迁移到新的库。此外,引用[3]中的错误提示提到找不到某个aar文件,这可能是因为依赖版本不正确或仓库配置有问题。 接下来,我需要给用户提供逐步的解决方案。首先建议他们更新依赖到ffmpeg-kit的LTS版本,比如5.1.0-LTS,并替换原来的flutter_ffmpeg。然后检查build.gradle中的仓库配置,确保包含了JitPack或其他必要的仓库。同时,清理和重新构建项目也是必要的步骤,以确保所有依赖项正确下载和链接。 另外,用户可能还需要处理平台相关的配置,比如Android和iOS的设置。例如,在Android的build.gradle中设置packagingOptions,避免重复文件导致的冲突。对于iOS,可能需要更新Podfile中的配置,并运行pod install。 如果问题依旧存在,可能需要检查网络是否正常,或者尝试切换不同的版本,如非LTS版本。最后,如果所有方法都无效,建议用户查阅官方文档或提交issue以获得进一步支持。 在生成相关问题的时候,应该围绕依赖问题、版本迁移、配置调整等方面,帮助用户扩展可能遇到的疑问,比如如何迁移到新版本,如何配置仓库,或者如何处理平台特定的问题等。</think>### 解决方案:Flutter 项目中 `com.arthenica:mobile-ffmpeg-full-gpl:4.4.LTS` 依赖缺失问题 #### 1. **更新依赖库** 旧版 `flutter_ffmpeg` 已停止维护,建议迁移至官方推荐的 `ffmpeg-kit` 库: ```yaml dependencies: ffmpeg_kit_flutter: 5.1.0-LTS # 或 5.1.0 ``` 替换原有的 `flutter_ffmpeg: 0.4.2`,并运行 `flutter pub get`[^2]。 #### 2. **检查仓库配置** 在 `android/build.gradle` 中添加 JitPack 仓库: ```groovy allprojects { repositories { google() mavenCentral() maven { url "https://jitpack.io" } # 关键仓库配置[^3] } } ``` #### 3. **清理并重新构建** ```bash flutter clean # 清理缓存 flutter pub cache repair # 修复依赖缓存 flutter run # 重新构建项目 ``` #### 4. **检查平台配置** - **Android**:在 `android/app/build.gradle` 中添加: ```groovy android { packagingOptions { pickFirst '**/libc++_shared.so' # 避免 NDK 库冲突 } } ``` - **iOS**:执行 `pod install` 更新 CocoaPods 依赖。 #### 5. **网络与代理问题** 确保 Gradle/Maven 仓库可访问,若使用代理需在 `gradle.properties` 配置: ```properties systemProp.https.proxyHost=your.proxy systemProp.https.proxyPort=8080 ``` #### 6. **版本回退(临时方案)** 若需强制使用旧版本,尝试修改依赖声明: ```yaml dependencies: ffmpeg_kit_flutter: 4.4.LTS # 注意兼容性风险[^1] ``` --- ###
评论 11
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值