java - 运行 Flutter 应用时出现 "Could not connect to the Gradle daemon"和 IP 地址问题

Question

我正在尝试在 Mac M1 上启动 Flutter 应用(Flutter 版本 2.10.3)。

我对文件 android/app/build.gradle 进行了下一次更新:

我的一些 Android 设置:

• compileSdkVersion 从 28 到 32
• targetSdkVersion 从 28 到 32
• android/build.gradle:ext.kotlin_version = '1.5.31'
• android/gradle/wrapper/gradle-wrapper.properties:distributionUrl=https\://services.gradle.org/distributions/gradle-6.9-all.zip >

我在模拟器 API 32 (Android 12L) 上运行该应用，但 Gradle 抛出异常。

日志:

...
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...

FAILURE: Build failed with an exception.

* What went wrong:
Could not connect to the Gradle daemon.
Daemon uid: fd2e13e6-2566-45f5-8766-4fedc7775cb0 with diagnostics:
Daemon pid: 11467
  log file: /Users/<username>/.gradle/daemon/6.9/daemon-11467.out.log
----- Last  20 lines from daemon log file - daemon-11467.out.log -----
2022-04-22T14:07:40.973+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding remote address /fe80:0:0:0:4a:4965:170f:6161%en0
2022-04-22T14:07:40.973+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding remote address /192.168.1.251
2022-04-22T14:07:40.973+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding IP addresses for network interface lo0
2022-04-22T14:07:40.974+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Is this a loopback interface? true
2022-04-22T14:07:40.974+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Ignoring remote address on loopback interface /fe80:0:0:0:0:0:0:1%lo0
2022-04-22T14:07:40.974+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding loopback address /0:0:0:0:0:0:0:1%lo0
2022-04-22T14:07:40.974+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.InetAddresses] Adding loopback address /127.0.0.1
2022-04-22T14:07:40.976+0200 [DEBUG] [org.gradle.internal.remote.internal.inet.TcpIncomingConnector] Listening on [bf4f42c3-7339-4aa4-8277-33e3ae19a1aa port:55627, addresses:[localhost/127.0.0.1]].
2022-04-22T14:07:40.982+0200 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] Daemon starting at: Fri Apr 22 14:07:40 CEST 2022, with address: [bf4f42c3-7339-4aa4-8277-33e3ae19a1aa port:55627, addresses:[localhost/127.0.0.1]]
2022-04-22T14:07:40.982+0200 [INFO] [org.gradle.launcher.daemon.server.DaemonRegistryUpdater] Advertising the daemon address to the clients: [bf4f42c3-7339-4aa4-8277-33e3ae19a1aa port:55627, addresses:[localhost/127.0.0.1]]
2022-04-22T14:07:40.982+0200 [DEBUG] [org.gradle.launcher.daemon.server.DaemonRegistryUpdater] Advertised daemon context: DefaultDaemonContext[uid=fd2e13e6-2566-45f5-8766-4fedc7775cb0,javaHome=/Applications/Android Studio.app/Contents/jre/Contents/Home,daemonRegistryDir=/Users/<username>/.gradle/daemon,pid=11467,idleTimeout=10800000,priority=NORMAL,daemonOpts=--add-opens,java.base/java.util=ALL-UNNAMED,--add-opens,java.base/java.lang=ALL-UNNAMED,--add-opens,java.base/java.lang.invoke=ALL-UNNAMED,--add-opens,java.prefs/java.util.prefs=ALL-UNNAMED,-Xmx1536M,-Dfile.encoding=UTF-8,-Duser.country=NL,-Duser.language=ca,-Duser.variant]
2022-04-22T14:07:40.983+0200 [DEBUG] [org.gradle.launcher.daemon.registry.PersistentDaemonRegistry] Storing daemon address: [bf4f42c3-7339-4aa4-8277-33e3ae19a1aa port:55627, addresses:[localhost/127.0.0.1]], context: DefaultDaemonContext[uid=fd2e13e6-2566-45f5-8766-4fedc7775cb0,javaHome=/Applications/Android Studio.app/Contents/jre/Contents/Home,daemonRegistryDir=/Users/<username>/.gradle/daemon,pid=11467,idleTimeout=10800000,priority=NORMAL,daemonOpts=--add-opens,java.base/java.util=ALL-UNNAMED,--add-opens,java.base/java.lang=ALL-UNNAMED,--add-opens,java.base/java.lang.invoke=ALL-UNNAMED,--add-opens,java.prefs/java.util.prefs=ALL-UNNAMED,-Xmx1536M,-Dfile.encoding=UTF-8,-Duser.country=NL,-Duser.language=ca,-Duser.variant]
2022-04-22T14:07:40.987+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on daemon addresses registry.
2022-04-22T14:07:40.988+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
2022-04-22T14:07:40.993+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
2022-04-22T14:07:40.993+0200 [LIFECYCLE] [org.gradle.launcher.daemon.server.Daemon] Daemon server started.
2022-04-22T14:07:40.994+0200 [DEBUG] [org.gradle.launcher.daemon.bootstrap.DaemonStartupCommunication] Completed writing the daemon greeting. Closing streams...
2022-04-22T14:07:40.996+0200 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] stopOnExpiration() called on daemon
2022-04-22T14:07:40.996+0200 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] awaitExpiration() called on daemon
2022-04-22T14:07:40.996+0200 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] daemon is running. Sleeping until state changes.
----- End of the daemon log -----

...

Answer 1

当我将 ProtonVPN 的设置更改为不太安全的配置时，问题就消失了。有一个功能是 [Kill Switch]( https://protonvpn.com/support/what-is-kill-switch/，可以保护您的 IP 地址，以防您意外失去与 ProtonVPN 服务器的连接。 [...] 这意味着即使在 ProtonVPN 重新连接之前您无法使用互联网，您的 IP 地址和 DNS 查询不会被暴露。