Status Update
Comments
lb...@gmail.com <lb...@gmail.com>
bi...@google.com <bi...@google.com>
pa...@google.com <pa...@google.com>
tn...@google.com <tn...@google.com>
lb...@gmail.com <lb...@gmail.com> #3
Android Studio Ladybug | 2024.1.3 Canary 2
Build #AI-241.18034.62.2413.12109192, built on July 18, 2024
Runtime version: 21.0.3+-12099254-b509.4 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 3072M
Cores: 16
Registry:
ide.images.show.chessboard=true
Non-Bundled Plugins:
com.github.drjacky.avocado (3.5.5)
cn.jxzhang.plugin.json-formatter (1.4)
com.intellij.marketplace (241.18034.82)
Show As ... (1.0.3)
String Manipulation (9.14.1)
GenerateSerialVersionUID (3.0.3)
idea.plugin.protoeditor (241.15989.49)
com.steve.plugins.autoscroll (1.1)
com.dethlex.numberconverter (2.0.1)
izhangzhihao.rainbow.brackets (2024.2.5-241)
com.ppismerov.ksvu (0.0.1)
net.aquadc.mike.plugin (0.32)
com.developerphil.adbidea (1.6.17)
GenerateSerializationHelpers (1.0.6)
cn.yiiguxing.plugin.translate (3.6.2)
tn...@google.com <tn...@google.com>
tn...@google.com <tn...@google.com> #4
The fix hasn't been released yet. It was integrated on the 19th, the day after the last canary was built. It should be included in canary 3.
lb...@gmail.com <lb...@gmail.com> #5
"Fixed" means I can check it out. Without me being able to verify it, why change to "fixed" ?
Who will tell me when I can check it out this way...
tn...@google.com <tn...@google.com> #6
Bugs get auto-tagged by a bot when the fixes are released to each version. Take a look at
tn...@google.com <tn...@google.com> #7
(There is no "future fix" status in this bug tracker.)
lb...@gmail.com <lb...@gmail.com> #8
The point in subscribing to the issue I've created is that eventually I will be able to check it out when it's truly fixed.
Right now it doesn't have this ability. Marking as "fixed" doesn't mean anything. Could be published a month from now, and even then not really fixed.
I've scheduled the email to be later, to remind me...
tn...@google.com <tn...@google.com> #9
Again, there will be a comment added here on this bug by the bot immediately when the bug is included in a release.
lb...@gmail.com <lb...@gmail.com> #10
Are you sure it will notify me?
js...@google.com <js...@google.com> #11
Take a look at
for an example, issue 347167978 . comment #10
Just
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 | 2024.1.3 Canary 1
Android Gradle Plugin 8.7.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!
an...@google.com <an...@google.com> #12
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 | 2024.1.3 Canary 3
- Android Gradle Plugin 8.7.0-alpha03
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!
lb...@gmail.com <lb...@gmail.com> #13
tn...@google.com <tn...@google.com> #14
Thanks for confirming!
Description
DESCRIBE THE ISSUE IN DETAIL:
STEPS TO REPRODUCE:
The bug is that it claims we are using too new APIs here, even though I've checked that it's only on the newest one, of API 35 and above...
Studio Build: Version of Gradle Plugin: Version of Gradle: Version of Java: OS: