Status Update
Comments
da...@gmail.com <da...@gmail.com> #2
The attached Build Scan log shows that the emulator process crashed unexpectedly. Could you rerun your task with --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
to get more information about the emualtor process logs?
ar...@google.com <ar...@google.com>
je...@google.com <je...@google.com> #3
l8...@gmail.com <l8...@gmail.com> #4
No idea why the scan does not contain log information, here you are:
xo...@google.com <xo...@google.com> #5
The link in --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
, the emulator process output its kernel logging to stdout. Do you see any stacktrace or segfault in the log?
l8...@gmail.com <l8...@gmail.com> #6
That's strange, the repo and the build is public... But I attached the logs as file
xo...@google.com <xo...@google.com> #7
I looked into the logs and it turns out, the runner didn't have enough disk space. I guess the root cause is the Gradle update causing another Gradle major version (and its new transform-4) folder to cache was too much. Anyway, a better error message of the exit code of GMD would be helpful.
l8...@gmail.com <l8...@gmail.com> #8
Thanks for uploading the log! Yes, the emulator kernel log says the issue was the insufficient disk space:
2024-04-02T18:31:45.7078429Z ERROR | Not enough space to create userdata partition. Available: 7177.027344 MB at /home/runner/.config/.android/avd/gradle-managed/dev34_aosp_atd_x86_64_Pixel_2.avd, need 7372.800000 MB.
Also, I agreed that GMD should diagnose errors and can provide better messages.
Let me rename this issue's title to improve the error message for disk space error.
xo...@google.com <xo...@google.com> #9
I've added a fix that will surface all error messages from the emulator in the exception when it closes unexpectedly.
l8...@gmail.com <l8...@gmail.com> #10
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat | 2024.3.1 Canary 2
- Android Gradle Plugin 8.9.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
xo...@google.com <xo...@google.com> #11
I've submitted fixes for this in all the available branches. It should already be fixed in Meerkat Feature Drop nightly builds, in case you want to try the very tip of development; otherwise, it should be available in the forthcoming releases:
- Canary channel: Meerkat Feature Drop Canary 5
- Beta channel: Meerkat Release Candidate 2
- Stable channel: Ladybug Feature Drop Patch 2
Thank you once again for the report.
an...@google.com <an...@google.com> #12
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat Feature Drop | 2024.3.2 Canary 5
- Android Gradle Plugin 8.10.0-alpha05
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
an...@google.com <an...@google.com> #13
The fixes for this issue are now also available in:
- Android Studio Meerkat | 2024.3.1 RC 2
- Android Gradle Plugin 8.9.0-rc02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
ch...@gmail.com <ch...@gmail.com> #14
Gelodichkhaidze
an...@google.com <an...@google.com> #15
Further fixes for this issue are now available in:
- Android Studio Meerkat Feature Drop | 2024.3.2 Canary 6
- Android Gradle Plugin 8.10.0-alpha06
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com <an...@google.com> #16
The fixes for this issue are now also available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Patch 2
- Android Gradle Plugin 8.8.2
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
No signature of method: org.gradle.api.internal.provider.DefaultProviderFactory.gradleProperty() is applicable for argument types: (String) values: [com.android.tools.utp.GradleAndroidProjectResolverExtension.enable]
Possible solutions: hasProperty(java.lang.String)
Studio Build:Meerkat | 2024.3.1 Beta 1
Version of Gradle Plugin:6.1.1
Version of Gradle:4.0.1
Version of Java:1.8
OS:window 10