Fixed
Status Update
No update yet.
Comments
xa...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ad...@google.com
Almost 2 months later and this is still broken
xa...@google.com
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
da...@google.com
jb...@google.com What is the update on this?
da...@google.com
xa...@google.com
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
hu...@google.com
Any ETA on next release?
de...@google.com
Still broken and not updated? --package_file argument is not usable in it's current form on 26.1.1 straight from the developer site.
sa...@google.com
Comfirmed that this seems to still be broken. Can we have an update please?
```
(15:58:11) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --version
26.1.1
(15:58:17) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --install --package_file=package_file
Warning: Unknown argument --package_file=package_file
```
```
(15:58:11) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --version
26.1.1
(15:58:17) C02W513SHTD8:files aso$ /opt/android-sdk-macosx/tools/bin/sdkmanager --install --package_file=package_file
Warning: Unknown argument --package_file=package_file
```
sa...@google.com
Hi, is there any update to this issue? Thanks.
da...@google.com
Hi Google. You claim it's been fixed on master, but we haven't had a new release since the broken version 26.1.1. Can you please release the fix?
da...@google.com
an...@google.com
Yeah, still not fixed --'
bu...@gmail.com
Can't believe this still isn't fixed 2 years later for a command line utility that sits on the main dev site.
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.