Status Update
Comments
xa...@google.com <xa...@google.com> #2
Interestingly I did not see this on my 2nd run, so this is likely cached by the SDK Manager. Still it should never be displayed under normal circumstances.
ad...@google.com <ad...@google.com> #3
I imagine that this is outside the scope of GMDs, correct? That is, the behavior needs to be change on the SDK Manager side? If so, I'll remove Daniel as the assignee.
xa...@google.com <xa...@google.com> #4
It's mostly a problem when using the GMD though. if the SDK Manager team does not have time, we should go and fix it because spamming the build log is not a good thing.
da...@google.com <da...@google.com> #5
I believe we pass the logger into the manager, so this should be a fairly easy fix.
da...@google.com <da...@google.com>
hu...@google.com <hu...@google.com> #6
I can still repro this issue without --info
.
Steps to repro:
- Make sure to delete system images from Android/Sdk directory.
- Run setup task.
xa...@google.com <xa...@google.com> #7
I think it's fine to have it with --info. This is a verbose output already.
hu...@google.com <hu...@google.com> #8
I agreed.
Actually, I was able to reproduce the issue without --info
however after running ./gradlew --stop
, I'm no longer able to reproduce the issue. I'm closing this bug again.
de...@google.com <de...@google.com> #9
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 Dolphin Canary 9 (2021.3.1.9)
- Android Gradle Plugin 7.3.0-alpha09
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!
sa...@google.com <sa...@google.com> #10
This issue has been fixed, not seeing any spamming log info
Tested Android studio version:
Dolphin Canary 9 (2021.3.1.9)[8473230]
sa...@google.com <sa...@google.com> #11
I can able to repro this bug in windows.
Steps followed:
- Delete
.android/avd/gradle-managed
folder - Restart machine
- Open Studio and reopen project and run
./gradlew app:device1Setup
I have used below code in build.gradle file.
testOptions {
devices {
device1 (com.android.build.api.dsl.ManagedVirtualDevice) {
device = "Pixel 2"
apiLevel = 30
systemImageSource = "google"
}
}
}
da...@google.com <da...@google.com> #12
Moving to P2 as it only happens when the download manifest needs to be re-parsed.
da...@google.com <da...@google.com>
an...@google.com <an...@google.com> #13
The fixes for this issue are now also available in:
- Android Studio Iguana | 2023.2.1 Canary 14
- Android Gradle Plugin 8.3.0-alpha14
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
Using Gradle Managed Device and running the setup task, I see a lot of lines like this:
We need to either run the SDK manager in silent mode (and possibly hook the more verbose output to gradle's verbose output), or just fix the SDK Manager (if it does not support different verbosity levels)
Now that we are using this from the command line via Gradle this is really important.