Selecting new variant in "Build Variants" tab not updating build [171501839]

Duplicate

of 142608498

Bug

Status Update

No update yet.

Description

ma...@trala.com

created issue #1

Oct 23, 2020 10:35PM

Before upgrading to AS 4.1, I could select an active build in the Build Variant tab. This would rebuild correctly and could be confirmed in the BuildConfig.java file. Now this doesn't happen. I have to change the variant in the tab, then to an explicit Build before my BuildConfig is updated properly. This is worrisome now our developers are building and testing incorrect build types, even after selecting the correct variant in the tab.

Build: AI-201.8743.12.41.6858069, 202009231536,

AI-201.8743.12.41.6858069, JRE 1.8.0_242-release-1644-b3-6222593x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.15.7, screens 1680x1050; Retina

AS: 4.1; Kotlin plugin: 1.4.10-release-Studio4.1-1; Android Gradle Plugin: 4.1.0; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: LLDB 3.1 (revision: 3.1.4508709); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (not found)

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Comments

uc...@google.com <uc...@google.com> Oct 23, 2020 11:59PM

Assigned to an...@google.com.

xa...@google.com <xa...@google.com> Oct 27, 2020 11:30PM

Reassigned to so...@google.com.

so...@google.com <so...@google.com> #2Oct 28, 2020 10:49AM

Weird "? extends" declarations floating in the middle of nowhere?

ma...@trala.com <ma...@trala.com> #3Oct 28, 2020 05:52PM

I've tried the build the correct variant in the build output tool window, didn't change the behavior. I've tried the set default trick under the product flavors in build.gradle, no luck.

I attached the log. It just switched back to mockDebug on me after I had prodDebug build variant selected and building properly (confirmed in BuildConfig, confirmed in watching Build output, etc). I updated my versionName and pressed Sync. I'm pretty sure the Sync switched it back to mockDebug.

idea.log

1.8 MB

View

Download

ma...@trala.com <ma...@trala.com> #4Nov 2, 2020 06:30PM

As I've grown used to identifying when this will happen. I've got the experimental setting applied, using "getIsDefault().set(true)" in my desired flavors in my app.gradle. I've ran Sync a few times doing some branch rebasing. What consistently happens is my desired build variant is selected (stagingDebug), it's even showing as building correctly in the Build terminal, and my BuildConfig file shows stagingDebug. When I click run it goes to deploy mockDebug flavor. Now to fix it I have to select a completely different build variant (prodDebug) and now it will deploy correctly.

idea1.log

5.1 MB

View

Download

ne...@gmail.com <ne...@gmail.com> #5Nov 7, 2020 08:08PM

We have the same issue as well. We are falling back to previous version until this is fixed.

so...@google.com <so...@google.com> #6Nov 11, 2020 12:05PM

Android Studio 4.1.1 includes fixes for several related problem. Could you let us know if it makes any difference for you? Thank you!

ma...@trala.com <ma...@trala.com> #7Nov 11, 2020 04:24PM

Works now! Thank you!

so...@google.com <so...@google.com> #8Nov 11, 2020 04:33PM

Status: Duplicate of

142608498

Thank you for confirming!