Fixed
Status Update
Comments
ch...@google.com <ch...@google.com> #2
Could you let me know the current version of AGP and Gradle in your project?
hu...@google.com <hu...@google.com> #3
I'm using Android Studio 4.0.0-beta01, AGP 4.0.0-beta01, and Gradle 6.0.
ch...@google.com <ch...@google.com> #4
I think it is expected? We don't offer the recommended upgrade dialog anymore. Lint warnings should be shown.
Bradley, do you know if it is expected to show balloon for this case?
Bradley, do you know if it is expected to show balloon for this case?
sm...@google.com <sm...@google.com> #5
If you mean the Android Gradle plugin update messages that also update the Gradle version these should be working as normal.
If you mean the link we provided to update only the Gradle wrapper version on an unsupported version then yes this won't be present in 4.0.
This is broken byhttps://github.com/JetBrains/intellij-community/commit/123242c4b23a90f7910193139aa4d3b2979d9647 (commit is very large). The changes to the external system error handling caused our handlers to not run for exceptions thrown with "org.gradle.*" or "groovy.lang.*". I'm guessing this one falls into that category.
If you mean the link we provided to update only the Gradle wrapper version on an unsupported version then yes this won't be present in 4.0.
This is broken by
hu...@google.com <hu...@google.com> #6
Right I meant #2 - the link to update the Gradle wrapper version.
Having this was helpful for users, so losing it would be a bit unfortunate. (Context: I discovered this when I tried to suggest the user to use the Android Studio quickfix:
sm...@google.com <sm...@google.com> #7
It will likely return once we move the handlers to the new api that the external system uses. Although I don't think we have any timeframe for this.
ch...@google.com <ch...@google.com>
ka...@google.com <ka...@google.com>
hu...@google.com <hu...@google.com> #8
From
Description
Android Studio 3.6 and earlier used to provide a quick fix for the users to update their Gradle version automatically, but that ability seems to have disappeared since Android Studio 4.0 (I'm observing this on Android Studio 4.0.0-beta01).
It would be great if we could add a test to prevent a future regression for this.