IssueTracker

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

1. Are you reporting this as a Developer or User?

2. Please confirm if you are using any third party application as a launcher?

3. Could you please provide a screen record of the issue for us to further investigate?

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

1. I am a User
2. No third party launcher using Default pixel launcher
3. I cannot for now recreate the bug but will enable screen record and upload when caught

Thank you for your response.

Once you are able to reproduce this bug, please upload the screen record of the issue.

Please upgrade to the latest release from the link Beta2.1.

If the issue still persists, please capture the new bug report along with the screen record and share it here.

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

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.

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.

I've added a fix that will surface all error messages from the emulator in the exception when it closes unexpectedly.

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!