Fixed
Status Update
Comments
ga...@linecorp.com <ga...@linecorp.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
ga...@linecorp.com <ga...@linecorp.com> #3
Almost 2 months later and this is still broken
be...@google.com <be...@google.com>
ma...@google.com <ma...@google.com> #4
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
ma...@google.com <ma...@google.com>
ap...@google.com <ap...@google.com> #6
What is the status of this item?
ga...@linecorp.com <ga...@linecorp.com> #7
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
ma...@google.com <ma...@google.com> #8
Any ETA on next release?
ma...@google.com <ma...@google.com> #9
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.
ma...@google.com <ma...@google.com> #10
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
```
cc...@google.com <cc...@google.com> #11
Hi, is there any update to this issue? Thanks.
ja...@gmail.com <ja...@gmail.com> #12
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?
je...@google.com <je...@google.com>
mi...@google.com <mi...@google.com>
ja...@gmail.com <ja...@gmail.com> #14
Can't believe this still isn't fixed 2 years later for a command line utility that sits on the main dev site.
an...@google.com <an...@google.com> #15
Any updates on this? The help for this command clearly states this argument is supported.
Description
Continuing report from b/307473787
I tried to followhttps://developer.android.com/topic/performance/baselineprofiles/create-baselineprofile#create-new-profile
I tried to perform testcases which are generated by baseline profile generator on Android Studio.
And tests are failed, because proguard rule was not installed on
benchmarkRelease
build type.In my case, there are several
dontwarn
rules, because many 3rd party libraries references missing classes.It seems that
benchmarkRelease
build type should be inherited proguard rules fromrelease
build type.Component used: Androidx Benchmark/baselineprofile plugin 1.2.0