# flutter_man **Repository Path**: mr_jianlong/flutter_man ## Basic Information - **Project Name**: flutter_man - **Description**: flutter 学习手册 - **Primary Language**: Unknown - **License**: Not specified - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2026-02-01 - **Last Updated**: 2026-05-22 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # flutter_man A new Flutter project. ## Getting Started This project is a starting point for a Flutter application. A few resources to get you started if this is your first Flutter project: - [Lab: Write your first Flutter app](https://docs.flutter.dev/get-started/codelab) - [Cookbook: Useful Flutter samples](https://docs.flutter.dev/cookbook) For help getting started with Flutter development, view the [online documentation](https://docs.flutter.dev/), which offers tutorials, samples, guidance on mobile development, and a full API reference. ## 问题分析 `flutter build apk --release` 卡住的原因: 1. **Gradle 版本兼容性问题**:你使用的是 Gradle 9.3.0(本地路径),这是一个较新的版本,可能与 Flutter Gradle 插件存在兼容性问题。 2. **依赖下载问题**:虽然配置了阿里云镜像,但某些依赖可能仍然无法正常下载。 3. **内存配置过高**:`-Xmx8G` 的堆内存配置可能超出系统可用内存,导致 Gradle 启动缓慢或卡死。 ## 解决方案 ### 方案一:清理缓存并重启构建 ```bash # 清理 Flutter 缓存 flutter clean # 清理 Gradle 缓存 cd android rm -rf .gradle build cd .. # 重新构建 flutter build apk --release -v ``` ### 方案二:调整 Gradle 内存配置 编辑 `android/gradle.properties`,适当降低内存配置: ```properties org.gradle.jvmargs=-Xmx4G -XX:MaxMetaspaceSize=2G -XX:ReservedCodeCacheSize=256m -XX:+HeapDumpOnOutOfMemoryError ``` ### 方案三:降低 Gradle 版本 将 `android/gradle/wrapper/gradle-wrapper.properties` 中的版本降低到更稳定的版本: ```properties distributionUrl=https\://services.gradle.org/distributions/gradle-8.5-all.zip ``` ### 方案四:添加超时配置 在 `android/gradle.properties` 中添加: ```properties org.gradle.connectionTimeout=60000 org.gradle.socketTimeout=60000 ``` ### 方案五:检查网络连接 确保网络可以正常访问 Maven 仓库。你可以尝试在浏览器中访问: - `https://maven.aliyun.com/repository/google` - `https://maven.aliyun.com/repository/public` --- **建议先尝试方案一**,清理缓存后加上 `-v` 参数运行,可以看到更详细的日志输出,有助于定位具体卡在哪个步骤。