IssueTracker

Thanks for the question! There is more information about this message in a tooltip, but that's not very discoverable. (I'll look to see if it's possible to add a hyperlink)

The brief answer to the question is that there are many ways of structuring a project's build files, only some of which are understood by the machinery underlying the AGP Upgrade Assistant. Probably the most common way of setting things up that will lead to this message is to have versions of dependencies and plugins specified using static constants defined in a class in buildSrc; it's unfortunate, because that is a nice way of centralizing dependency versions (though it does have downsides: any change to anything in buildSrc causes a full recompile of the project).

There's now a bit more documentation at https://developer.android.com/studio/build/agp-upgrade-assistant which goes into a little more detail about ways to structure the project so that it's understood.

I added a hyperlink pointing to the documentation, so hopefully it's clearer what the cause is and how users can move forward. Thanks again for the report.

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 Dolphin Canary 2 (2021.3.1.2)
• Android Gradle Plugin 7.3.0-alpha02

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!

It's still unclear. I read https://developer.android.com/studio/build/agp-upgrade-assistant and I don't see where there is an affirmative recommendation about best practices. I have a project that's been used for years and just did the recommended upgrade from stable Android Studio Bumblebee 2021.1.1 Patch 1 to Patch 2. After that I did the recommended upgrade for com.android.tools.build.gradle from 7.1.1 to 7.1.2. In the project-level build.gradle I have:

buildscript {
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
// 2/16/22 suggested by
// https://discuss.gradle.org/t/conflicts-with-xerces/25861
// xerces class conflict casting parser ant pulling in orgmob build.xml
        configurations.classpath.exclude group: 'xerces', module: 'xercesImpl'
        classpath 'com.android.tools.build:gradle:7.1.2'
        classpath 'com.google.gms:google-services:4.3.10'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.8.1'
    }
}
// and some other allprojects stuff

The web page just talks about buildSrc, which I'm not using. I've never gotten this error message before in the multiple years of using Android Studio. What specifically is supposed to be done differently?

I'm not sure I understand your situation. That project-level build.gradle file looks reasonable to me: did the Upgrade Assistant upgrade it successfully? When exactly did you get the "Cannot find AGP version in build files" diagnostic? Thanks!

Yesterday what happened to me is that I got the warning to upgrade the dependency on com.android.tools.build:gradle from 7.1.1 to 7.1.2, did so. Then I had build problems and the Upgrade Assistant appeared giving the complaint about not finding the AGP version, so I backed off the change.

Today I made the dependency change just like yesterday and it all worked. My Mac (Monterey 12.2.1) had been put to sleep overnight, but not restarted. Yesterday I had just upgraded to Android Studio Bumblebee 2021.1.1 Patch 2 from Bumblebee Patch 1 just before making the dependency change.

¯\(ツ)/¯