does anyone having problem after update Android Studio Arctic Fox Canary 5 (2020.3.1.5) ?

FAILURE: Build failed with an exception.

* What went wrong:
lateinit property variantName has not been initialized

Just clutching at straws here but did you also update gradle wrapper as well (should happen as part of update it prompts you for if you accept that)?

Android Studio Arctic Fox Canary 5 (2020.3.1.5) Android Gradle Plugin 7.0.0-alpha05 Gradle 6.8.1

I'm on 6.8 for some reason but probably shouldn't make too much difference

but, is it now working for you? after you update the gradle wrapper…

yeah, everything seems to be fine

I’ve just created a fresh new project and the error still occurring:

19:43:55: Executing task 'build'...

Executing tasks: [build] in project /Users/[my_user]/MyApplication/app


FAILURE: Build failed with an exception.

* What went wrong:
lateinit property variantName has not been initialized

Android Studio Arctic Fox Canary 5 (2020.3.1.5) Android Gradle Plugin 7.0.0-alpha05 Gradle 6.8

Change your gradle plugin to 4.1.0

@magnumrocha I have the same problem. @Sean Keane 4.1.0 won't support the latest Compose Alpha.

@darkmoon_uk I had a similar issue. This was the resolution. https://youtrack.jetbrains.com/issue/IDEA-252823 No mention of Compose in this thread though so it's worth a try.

the problem is Android Studio Arctic Fox Canary 5 (2020.3.1.5) only works with AGP 7.0.0-alpha05, we can’t downgrade AGP version

Have you a sample project I can check with?

a fresh new Android Project, created on Android Studio Arctic Fox Canary 5 (2020.3.1.5) :

2 sec and I'll check on my end.

the `gradle-wrapper.properties`:

#Thu Jan 28 19:43:08 WET 2021
distributionBase=GRADLE_USER_HOME
distributionUrl=https\://services.gradle.org/distributions/gradle-6.8-bin.zip
distributionPath=wrapper/dists
zipStorePath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME

No issues for me Executing tasks: [appassembleDebug] in project /Users/sean/AndroidStudioProjects/TestGradlePlugin

Task apppreBuild UP-TO-DATE

Task apppreDebugBuild UP-TO-DATE

Task appcompileDebugAidl NO-SOURCE

Task appcompileDebugRenderscript NO-SOURCE

Task appgenerateDebugBuildConfig

Task appgenerateDebugResValues

Task appgenerateDebugResources

Task appcheckDebugAarMetadata

Task appcreateDebugCompatibleScreenManifests

Task appextractDeepLinksDebug

Task appprocessDebugMainManifest

Task appprocessDebugManifest

Task appmergeDebugNativeDebugMetadata NO-SOURCE

Task appjavaPreCompileDebug

Task appmergeDebugShaders

Task appcompileDebugShaders NO-SOURCE

Task appgenerateDebugAssets UP-TO-DATE

Task appmergeDebugAssets

Task appcompressDebugAssets

Task appprocessDebugJavaRes NO-SOURCE

Task appmergeDebugResources

Task appcheckDebugDuplicateClasses

Task appdesugarDebugFileDependencies

Task appmergeDebugJniLibFolders

Task appmergeLibDexDebug

Task appmergeDebugNativeLibs NO-SOURCE

Task appstripDebugDebugSymbols NO-SOURCE

Task appvalidateSigningDebug

Task appwriteDebugAppMetadata

Task appwriteDebugSigningConfigVersions

Task appprocessDebugManifestForPackage

Task appprocessDebugResources

Task appmergeExtDexDebug

Task appcompileDebugKotlin

Task appcompileDebugJavaWithJavac

Task appcompileDebugSources

Task appdexBuilderDebug

Task appmergeProjectDexDebug

Task appmergeDebugJavaResource

Task apppackageDebug

Task appassembleDebug

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings BUILD SUCCESSFUL in 13s 28 actionable tasks: 28 executed Build Analyzer results available

Blank Activity

Same on my end. It just built. Did you reset your cache.

yes, I did, but I will do again, 1 sec.

Can you check all SDK build tools are also updated?

is that your setup?

I previously deleted entire

.gradle

folder and got the same (bugged) result so keen to hear how this goes...

Android Studio Arctic Fox | 2020.3.1 Canary 5 Build #AI-203.6682.168.2031.7101492, built on January 25, 2021 Runtime version: 11.0.8+10-b944.6842174 x86_64 VM: OpenJDK 64-Bit Server VM by N/A macOS 10.15.7 GC: G1 Young Generation, G1 Old Generation Memory: 4096M Cores: 24 Registry: external.system.auto.import.disabled=true Non-Bundled Plugins: com.mallowigi, com.vincentp.gruvbox-theme

I made the Update

Can you give me the build.gradle file?

Yes

Here's how I fixed it. Go to "Build Variant" -> Change to release -> Build -> Change back to debug -> Build.

I get the linter error when building from command line though, so my question would be how is that UI operation affecting the underlying Gradle invocation

That only works for building the app and not running it on a device

Umm... In summary does that mean that just clearing caches thoroughly fixed it?

Clearing the cache's for AS doesn't. Manually clearing the caches does. When you run the clean command it doesn't "Clean" everything. So a manual delete forces the .gradle and .idea to be re-created to the standard of the project. So I'm guessing its an issue with the template as my other existing projects didn't have this problem.

not working for me….

Back on laptop, about to give it a go... but in my previous attempts to fix this I had 'deep cleaned'

I discover the problem in a project that I was working before the AS update, then I’ve create a new project just to check if it was config Issue on my previous project

I just seen that my workspace.xml between my "new project" and the one I fixed is different.

The problem when seen here is not to do with the IDE as @magnumrocha says

sure, the Issue is on AGP 7.0.0-alpha05

I managed to get my second app that wasn't working - working.

Sean do you mean by when you selected the variant manually in the IDE?

Bottom left corner, where you have "Build Variant" change it

If so, it sounds like that caused the IDE to invoke Gradle with some flag to specify the variant.

Yep! And it seems by not declaring it in the CLI its having a hissy fit.

Hmm, so what's the flag to specify variant to the CLI 🤔

assembleDebug

Yep understand it ordinarily takes this from component of the task name

It seems if the Variant name is specified with the assemble task it works. I can install and run the project. So I'm guessing the issue here is the build doesn't have its default for debug in the CLI tool.

But this is definitely looking like a serious bug in

alpha05

If you want more variants you can just declare them in the .gradle file and re-import.

I'm kind of surprised something this major could get through the Gradle Plugin CI pipeline TBH, you'd think there would be a unit test for performing a variantless build on... anything.

Don't be fooled. Unit tests are only as good as the people who write them 😉

Thanks @Sean Keane! We're definitely in bat country with '`alpha11` and friends' - plenty of other bugs being reported as well.

thank you guys @darkmoon_uk @Sean Keane 👍

I can confirm I'm getting the same issues with my KMM project. Fingers cross this gets resolved quickly 🤞

This has been fixed in AGP 7.0.0-alpha07 😃

@Umit AYDIN As of now, 'only' two releases away 😨 https://mvnrepository.com/artifact/com.android.tools.build/gradle?repo=google It got recognised as a P1 in the Google Issue so they might bring it forward? Good thing we can work around it.

I hope they release the

7.0.0-alpha06

and

7.0.0-alpha07

together….