Fixed
Status Update
No update yet.
Comments
aa...@google.com
je...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
mi...@google.com
Almost 2 months later and this is still broken
se...@exaring.de
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
mi...@google.com
se...@exaring.de
jb...@google.com What is the update on this?
se...@exaring.de
What is the status of this item?
hu...@google.com
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
mi...@google.com
hu...@google.com
Any ETA on next release?
an...@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.
Description
Note: This is a bug in the Android Gradle Plugin, but I am not allowed to create an issue in the Android Gradle Plugin component.
ISSUE:
The
AidlCompileAndroid Gradle Plugin task is rarely, and completly randomly, failing with the exceptionIndexOutOfBoundsException: Index 0 out of bounds for length 0. See also the below stacktrace.Re-runing the same Gradle command, with the same input, always resolves this issue. Sometime we have to re-run multiple times though.
Because this issue appears randomly, and for a while now, it is hard for us to pinpoint the exact versions when this issue first appeared.
Currently we use APG 8.2.0 with Gradle 8.5 and build-tools 34.0.0.
We experience this issue only on our CI where all builds are running inside a separate docker container, and are therefore de-facto clean builds. However we are re-using the Gradle build-cache across our different stages. But the Gradle daemon is alwas spawned anew.
We only have one AIDL file, which is only in the sourceset of our
AndroidTVflavor:app/src/androidtv/aidl/com/example/FunInterface.aidl. And our project has a lot of app variants. There are two buildTypes (debug, release) and four product flavor dimensions (one dimension isplatformwhereAndroidTVis one of the flavors).Even though we enabled AIDL compilation for all variants it only fails when running
assembleAndroidTV...Releasefor theAndroidTVflavor.From what I understand the cause for this issue is that the AIDL output files are seemingly empty. However, after the job failed there is one valid Java file inside
app/build/generated/aidl_source_output_dir/androidtvInternalStandaloneProdRelease/out/com/example/FunInterface.java.STEPS TO REPRODUCE:
The build failure happens randomly and rarely, therefore I am not able to provide neither steps to reproduce nor an explicit repro-sample project.
VERSIONS:
Version of Gradle Plugin: 8.2.0
Version of Gradle: 8.5
Version of Java: OpenJDK 64-Bit Temurin-17.0.8+7
OS: Ubuntu 22.04.2 LTS