如果本文內(nèi)容對(duì)您有用滋觉，記得點(diǎn)個(gè)贊吧!
1.卡在 Running "flutter pub get" in xxx .解決方法
Mac上
//命令行輸入
vim ~/.bash_profile
//添加下面三行，保存
export PUB_HOSTED_URL=https://pub.flutter-io.cn
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn
export PATH=/Users/計(jì)算機(jī)名稱/flutter/bin:$PATH //下載的flutterSDK的路徑
//命令行輸入
source ~/.bash_profile
flutter -h
Windows 新增兩個(gè)環(huán)境變量
PUB_HOSTED_URL ===== https://pub.flutter-io.cn
FLUTTER_STORAGE_BASE_URL ===== https://storage.flutter-io.cn
2.在Android上調(diào)試時(shí)齐邦，提示Kotlin相關(guān)下載問(wèn)題椎侠。
檢查Kotlin版本和項(xiàng)目配置版本
build.gradle中的配置是否相同。
不同的話修改為相同的版本
3.導(dǎo)入項(xiàng)目或新建項(xiàng)目 運(yùn)行不起來(lái)
1.在運(yùn)行項(xiàng)目前需檢查 Gradle版本 Kotlin版本 AndroidSdk等的配置 是否和項(xiàng)目中的配置一致 如果不一致則需要修改項(xiàng)目中的配置
4.Gradle sync failed: Cause: error in opening zip file
復(fù)制Gradle zip包 到 項(xiàng)目.gradle中的對(duì)應(yīng)位置
5.卡在Running Gradle task ‘a(chǎn)ssembleDebug‘
https://blog.csdn.net/qq_41560865/article/details/107175819
6.Please configure Android SDK
https://stackoverflow.com/questions/21070268/intellij-idea-13-error-please-select-android-sdk
7.Flutter 項(xiàng)目打包 生成APK IPA
C:\Program Files\Java\jdk1.8.0_77\bin>
生成簽名文件：
keytool -genkey -v -keystore D:*******.jks -keyalg RSA -keysize 2048 -validity 10000 -alias ******
查看簽名：
keytool -list -v -keystore D:*****.jks
8.Flutter 布局中解決 鍵盤頂出固定在底部的widget和鍵盤遮擋輸入框的沖突
9.Flutter 項(xiàng)目真機(jī)調(diào)試一直處于loading...
在flutter開(kāi)發(fā)的時(shí)候一直loading
在安裝flutter的路徑底下進(jìn)入bin/cache措拇，然后把下圖的lockfile刪除我纪，然后重新跑一遍就好了
10.Flutter Waiting for another flutter command to release the startup lock
1.關(guān)閉Android Studio
2.打開(kāi)flutter安裝目錄/bin/cache
3.刪除lockfile文件
此時(shí)可在命令行再執(zhí)行flutter相關(guān)命令，完美解決
11.'!_debugLocked': is not true.
使用Future去包含路由跳轉(zhuǎn)：
Future.delayed(Duration.zero,(){
Navigator.of(context).push(MaterialPageRoute(
builder: (BuildContext context) => routes.buildPage(path, params),
));
});
Future.delayed(Duration.zero,(){
Navigator.of(context).push(MaterialPageRoute(
settings: RouteSettings(name: path),
builder: (BuildContext context) => routes.buildPage(path, params),
fullscreenDialog: true,
));
});
