Fixed
Status Update
Comments
ac...@google.com <ac...@google.com>
je...@google.com <je...@google.com>
je...@google.com <je...@google.com> #2
Please re-assign to UX. It was a UX team request to make them appear this way.
They, however, are supposed to be black solid black in bound to a variable (I don't know why it is important).
je...@google.com <je...@google.com> #3
these should be the [...] button. I don't know where that request came from but the pattern should be similar to what you see here.
an...@gmail.com <an...@gmail.com> #4
Setting as P2 as it is a minor UX issue.
an...@google.com <an...@google.com> #5
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 Ladybug Feature Drop | 2024.2.2 Canary 1
- Android Gradle Plugin 8.8.0-alpha01
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!
lu...@gmail.com <lu...@gmail.com> #6
Kdirorifkg.
Description
DESCRIBE THE ISSUE IN DETAIL:
When using the older
android.ndkDirectory
API that eagerly evaluates the value, it evaluates to the proper directory path. However, when using theandroidComponents.sdkProvider.ndkDirectory
provider, gradle fails withCannot query the value of this provider because it has no value available.
.This seems to only affect
ndkDirectory
. Other things, likesdkDirectory
work fine.STEPS TO REPRODUCE:
./gradlew printEager
. It should successfully print the SDK and NDK paths../gradlew printLazy
. It should successfully print the SDK path, but crash when attempting to print the NDK path.ATTACH LOG FILES
(Attached outputs of gradle commands)