Я попробовал запустить «futter run» для недавно созданного проекта flutter, но он застрял в разрешении зависимостей и в журналах появились ошибки ниже.
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.
Это странно, потому что на днях все работало идеально, а я ничего не менял и не устанавливал.
Я попробовал запустить «futter run» для недавно созданного проекта flutter, но он застрял в разрешении зависимостей и в журналах появились ошибки ниже.
[code]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. [/code]
Это странно, потому что на днях все работало идеально, а я ничего не менял и не устанавливал.
Я пытаюсь запустить приложение Flutter (версия Flutter 2.10.3) на Mac M1.
Я внес следующие обновления в файл android/app/build.gradle :
Некоторые из моих настроек Android:
compileSdkVersion от 28 до 32
targetSdkVersion от 28 до 32...
Я пытаюсь запустить приложение Flutter (версия Flutter 2.10.3) на Mac M1.
Я внес следующие обновления в файл android/app/build.gradle :
Некоторые из моих настроек Android:
compileSdkVersion от 28 до 32
targetSdkVersion от 28 до 32...
Так что я вроде новичок, чтобы трепетать, и я пытаюсь сделать небольшой проект, чтобы немного учиться, и я наткнулся на проблему, которая немного заставляла меня побить голову на клавиатуру.
Я сделал класс Singleton, в котором хранится некоторые...
Я использую очень сложную настройку для тестирования различных закрытых веб-страниц. Я использую jenkins для запуска тестов python-selenium в образе докера. Таким образом, я полностью независим от среды Jenkins и могу создавать свою собственную...
РЕДАКТИРОВАТЬ: я решил эту проблему, исправив все незначительные ошибки в моем коде, а также добавив следующую строку кода в файл gradle.properties. Это увеличивает максимальный размер кучи для демона Kotlin.
kotlin.daemon.jvm.options=-Xmx2g