Could not connect to the Gradle daemon. while running 'flutter run'

Question

I tried running 'flutter run' on newly created flutter project but it stucks in Resolving dependencies and got below errors in logs.

Launching lib/main.dart on ASUS X00DDA in debug mode...
Initializing gradle...                                       1.2s
Resolving dependencies...
* Error running Gradle:
Exit code 1 from: C:\Users\username\Desktop\Project\myprojectr\android\gradlew.bat app:properties:
Starting a Gradle Daemon, 14 stopped Daemons could not be reused, use --status for details


FAILURE: Build failed with an exception.

* What went wrong:
Could not connect to the Gradle daemon.
Daemon uid: 6a5529f2-392b-4727-b66f-78a2fab605bf with diagnostics:
Daemon pid: 14840
  log file: C:\Users\arjay24\.gradle\daemon\4.1\daemon-14840.out.log
----- Last  20 lines from daemon log file - daemon-14840.out.log -----
15:00:39.882 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
15:00:39.888 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:00:39.889 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:00:39.890 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:00:39.891 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:00:39.891 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:00:39.892 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:00:39.893 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:00:39.893 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:00:39.893 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:00:49.885 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
15:00:49.885 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:00:49.886 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:00:49.886 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:00:49.887 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:00:49.887 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
15:00:49.888 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
15:00:49.889 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
15:00:49.889 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process (pid: 13900, operation: ). Will attempt to ping owner at port 61789
15:00:49.889 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process. I was unable to read on which port the owner listens for lock access requests.
----- End of the daemon log -----


* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

Please review your Gradle project setup in the android/ folder.

It's weird because the other day it works perfectly and I haven't changed or installed anything.

What you can try is `flutter clean` `flutter upgrade` and `Invalidate caches and restart`; if you are using Android Studio/IntelliJ. — Bostrot, Jul 01 '18 at 11:07
I am using visual studio code and android studio for IDEs both shows the same error. I already tried flutter clean and flutter upgrade but no success. — ilovejavaAJ, Jul 01 '18 at 11:09
Sounds basic but did you try to restart your pc so adb etc restarts itself? — Bostrot, Jul 01 '18 at 11:25
@Bostrot Yes restart the pc and kill and then restart adb but still exist. :'( — ilovejavaAJ, Jul 01 '18 at 11:43
Is there some news on the matter? I have a similar problem on Windows as well. And it is somehow has started today... — Artem Bilan, Dec 20 '18 at 18:17
If you have a vpn with a kill switch, try turning it off that worked for me — ikben, Dec 22 '22 at 08:19

score 11 · Answer 1 · answered Sep 13 '21 at 16:44

11

I solved it by disconnecting from my VPN. Seems weird but it worked :-)

answered Sep 13 '21 at 16:44

F.Tepel

140
1
6

1

One Line answers can always go in the comments! – gtxtreme Sep 13 '21 at 17:12
Thank you, this worked for me! – Miguel Jiménez Nov 02 '21 at 18:04
In case of ProtonVPN turning KillSwitch off works as well. – Jakub Kuszneruk Feb 18 '23 at 13:20

score 0 · Answer 2 · answered Jan 19 '21 at 19:01

The issue doesn't seem to be caused by Flutter. Inspecting the logs, the instance couldn't connect to the Gradle daemon due to "The file lock is held by a different Gradle process". If you're still having this issue, could you try removing the lock files in the Gradle cache and try running the app again?

score 0 · Answer 3 · answered Jan 02 '22 at 19:25

0

I also had incorrect path of distributionUrl in your_root_directory/android/gradle/wrapper/gradle-wrapper.properties

It worked after correcting the path: distributionUrl=https://services.gradle.org/distributions/gradle-6.7-all.zip

answered Jan 02 '22 at 19:25

Baba King

1
1

While I agree with you, I think, this should be a comment on the initial question, not an answer. – Tim Brückner Jan 02 '22 at 23:43

score 0 · Answer 4 · answered Jun 15 '22 at 05:48

0

I got an idea from @F.Tepel answer, After uninstalling my antivirus my issue was fixed.

answered Jun 15 '22 at 05:48

Abbas Jafari

1,492
2
16
28

score -2 · Answer 5 · edited May 23 '21 at 02:23

-2

I had the same issue. I solved the issue by upgrading the gradle by changing the distributionUrl in the your_root_directory/android/gradle/wrapper/gradle-wrapper.properties file.

You can refer here for the instructions to upgrade gradle

edited May 23 '21 at 02:23

Undo

25,519
37
106
129

answered May 21 '21 at 18:35

Sahil Kumar

1
1

Could not connect to the Gradle daemon. while running 'flutter run'

5 Answers5