Fixed
Status Update
Comments
da...@google.com <da...@google.com> #3
Sorry, I was wrong in my assessment earlier. This is not a caching issue. I misunderstood the initial bug since I was worrying about reports of view binding classes not resolving.
I can reproduce this issue easily, although I'm not yet sure what I can do about it (we don't write the logic behind autocompletes, we just provide answers to the underlying IDE framework when they ask us questions). I'll schedule a bit of time later to take a look, after getting through a few other priorities.
da...@google.com <da...@google.com> #4
Thank you for the suggestion. This behavior should start rolling out in AS4.2 Canary 4 and after.
ni...@google.com <ni...@google.com> #5
Great, thanks!
Description
Android Studio version: 4.0 AGP version: 4.0.0
Description: The autocomplete experience for generated binding classes in Android Studio 4.0 (and possibly other versions) could be better. The search term "Binding" does not offer suggestions for any binding classes.
Steps to reproduce:
buildFeatures.viewBinding = true
MainActivity.kt
, begin declaring a new variablebinding:
binding
, start typing "Binding"ActivityMainBinding
is not one of the suggested classes in the autocomplete popup window. The same can be said for the search term "Main".