Status Update
Comments
bl...@google.com <bl...@google.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?
re...@google.com <re...@google.com>
ar...@google.com <ar...@google.com> #3
dm...@ownid.com <dm...@ownid.com> #4
No idea why the scan does not contain log information, here you are:
ar...@google.com <ar...@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?
ar...@google.com <ar...@google.com> #6
That's strange, the repo and the build is public... But I attached the logs as file
dm...@ownid.com <dm...@ownid.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.
ar...@google.com <ar...@google.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.
dm...@ownid.com <dm...@ownid.com> #9
I've added a fix that will surface all error messages from the emulator in the exception when it closes unexpectedly.
ar...@google.com <ar...@google.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!
ar...@google.com <ar...@google.com>
sg...@google.com <sg...@google.com>
sg...@google.com <sg...@google.com> #11
We're working on a fix for this problem, it will be available in our next version release in a few weeks.
ap...@google.com <ap...@google.com> #12
Branch: androidx-main
commit 0087efbd0a8ce75be8619e8718d217a1c771cf16
Author: Guangjie Shi <sgjerry@google.com>
Date: Fri Aug 25 18:27:54 2023
include proguard in the gradle
Test: local build
Bug: 288120539
Change-Id: I1b5a4cc823aeae3dbadcc9d949b02fc5d7ca86dc
M credentials/credentials-play-services-auth/build.gradle
sg...@google.com <sg...@google.com> #13
The fix will be out in our release next week.
na...@google.com <na...@google.com> #14
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.credentials:credentials-play-services-auth:1.2.0-beta04
Description
Version used: androidx.credentials:credentials-play-services-auth:1.0.0-alpha09
Looks like there is no R8/Proguard rules embedded in the lib.
There was a commit specifically for that:
but I cannot find a `proguard.txt` file in `credentials-play-services-auth-1.0.0-alpha09.aar`
I know that there is an instruction to add rules manually
but why we have to do this manually?