Unable to switch to debug build variant in Android Studio

Question

I've switched to release build variant and configured signingConfigs. Now when I try to check the debug build variant from the drop down menu it switches immediately back to the release build variant. So I'm not able to run my app in debug mode any more.

apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'
apply plugin: 'kotlin-kapt'
apply plugin: 'realm-android'

android {
    signingConfigs {
        config {
            ...
        }
    }

    compileSdkVersion rootProject.compileSdkVersion
    buildToolsVersion rootProject.buildToolsVersion

    defaultConfig {
        applicationId "com.kost.foo"
        minSdkVersion rootProject.minSdkVersion
        targetSdkVersion rootProject.targetSdkVersion
        versionCode 2
        versionName "1.1"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        ndk {
            abiFilters 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
        }
        externalNativeBuild {
            cmake {
               ...
            }
        }
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
            debuggable true
            signingConfig signingConfigs.config
        }
    }

    sourceSets {
        main.java.srcDirs += 'src/main/kotlin'
        main {
            jniLibs.srcDirs = ['src/main/jni']
        }
    }

    externalNativeBuild {
        cmake {
            path 'src/main/jni/CMakeLists.txt'
        }
    }
}

kapt {
    generateStubs = true
}

repositories {
    maven { url 'https://github.com/linchaolong/stetho-realm/raw/master/maven-repo' }
    mavenCentral()

}

I've tried to revert all changes in build.gradle as it was before configuring, but with no luck.

Any ideas how to fix the issue?

I cannot say I've solved it as I still don't know what caused the problem. But the fastest work around I found was to push the project to git (bitbucket in my case) and check it out from version control in a new project. — AlexKost, Mar 08 '17 at 04:33
I followed your work around and it did helped !!! Thanks @AlexKost — Pip, Mar 27 '17 at 09:03
@Igor Ganapolsky I was just playing around with different flags in order to get some more information and insight on what was going on. I removed it afterwords. — AlexKost, May 19 '17 at 03:12
@shizhen As I stated in the comment above I was bale to work around the problem. After that I never run again into the same problem, so I was unable to check any other solution. Some of them might provide a better one, though. The most upvoted answer seems to be outdated. — AlexKost, Sep 11 '18 at 03:42

score 32 · Answer 1 · answered May 22 '18 at 13:23

I had a similar problem where most of the Build menu items were greyed out.

'Sync project with Gradle files' didn't fix.

I noticed a 'Build Variants' toggle button on the bottom left of Android Studio (v 3.1.2) and with this was finally able to choose the variant I needed.

Maybe this will work for you too.

shizhen · Answer 2 · 2019-05-09T10:10:24.490

14

Maybe you have got your solution to this, just in case, i provide my solution here.

For Android Studio 2.x

It may because that you compile your dependent project using:

compile project('module_a')

Above setting will force your project to compile the release version of your modules. Just change it to below:

releaseCompile project(path: ':module_a', configuration: 'release')
debugCompile project(path: ':module_a', configuration: 'debug')

For Android Studio 3.x

You don't need to explicitly specify the build variant for a "module project". Just using

implementation project(':library')

will automatically help select the correct build variant.

Here is a detailed explanation: https://developer.android.com/studio/build/?utm_source=android-studio#variant_aware

For Android Studio 3.x Upgraded from 2.x

Delete the .idea folder under your project root directory and restart your Android Studio.

Below is the GUI screenshot:

Hope it helps!

edited May 09 '19 at 10:10

answered May 19 '17 at 06:11

shizhen

12,251
9
52
88

1

this is only for older gradle versions: [link](https://stackoverflow.com/questions/33718663/gradle-error-configuration-declares-dependency-which-is-not-declared), refer to post by @rockefelox for newer versions – Madura Anushanga Dec 09 '17 at 08:52
True. Since Android Studio 3.0, all the xxxCompile closures change to xxxImplementation. – shizhen Dec 11 '17 at 02:13
1

For Android Studio 3.1.2, you don't need to explicitly specify the build variant for a "module project". Just using implementation project(':library') will automatically help select the correct build variant. Here is a detailed explanation https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration?utm_source=android-studio#variant_aware . – shizhen Jun 18 '18 at 07:04

score 14 · Answer 3 · answered Nov 16 '17 at 12:41

14

Just need to cut ".idea" Folder and paste it outside Project root folder( For Back up if you need).These files will be auto regenerated. On Opening the project it"ll ask add module (app) to your project. You can ignore the same.

It set set default build variant to be "debug". You can see build variant tab on left corner or hover on "Monitor" Symbol on left bottom to get build variant option.

answered Nov 16 '17 at 12:41

deva11

881
10
25

This is the solution what worked for me in Android Studio 3.1.2 – rpattabi May 13 '18 at 11:33
Good to know that It helped you. :) – deva11 May 14 '18 at 02:29
worked for me also. Just deleted .idea folder and re-created workspace by reading build.gradle – Arthur Melo Aug 10 '18 at 19:07
1

i needed to remove and re-import the project as described here: https://stackoverflow.com/a/45950059/5443056 – Braden Holt Apr 07 '20 at 20:50
For some reason deleting `.idea` folder and `invalidate cache and restart` did not work. and deleting it and just restarting worked. – hushed_voice May 29 '20 at 15:41

score 10 · Answer 4 · answered Jul 11 '17 at 13:39

10

I just had the same issue. Solved it by closing Android Studio, removing the generated files and folders: .gradle, .idea, app/.externalNativeBuild, app/build, build, app/app.iml, ProjectName.iml, local.properties, then relaunching Android Studio and allowing it regenerate all these files from scratch.

answered Jul 11 '17 at 13:39

Andrew Starostin

514
1
4
12

2

Only had to delete `rm -rf ./.gradle ./app/.gradle .idea/caches/` – Afilu Jun 22 '19 at 06:22
\\ You saved my time .. thanks a lot @andrew – Muhamed El-Banna Aug 02 '23 at 22:34

score 6 · Answer 5 · answered May 19 '17 at 13:58

6

Had the same problem, solved creating a new temporary Build Type, Build > Edit Build Types, select Build Types and add a new one. Sync, then you can select the new build type, and then revert back to original Debug build type.

answered May 19 '17 at 13:58

rockefelox

61
1
3

Was the only solution that worked for me Android Studio 3.4.2 – ykonda Aug 05 '19 at 14:43
On Android Studio, these types of solutions are always the best. – Geraldo Neto Sep 16 '21 at 14:25

score 2 · Answer 6 · answered Jan 22 '18 at 08:05

Open your module setting. (Click F4)

Go to build types and create a new Build by clicking on plus(+) sign.

Name it anything, like "demo".

Duplicate all the data of debug build.

Now when you open Build Variant you will be able to switch to Debug as well as Demo.

score 1 · Answer 7 · answered Aug 08 '17 at 18:56

1

For me I was unable to switch to our 'devDebug' variant but I could switch to another variant like 'devRelease' and then 'devDebug'. So try switching to another variant first.

answered Aug 08 '17 at 18:56

checkmate711

3,301
2
35
45

score 1 · Answer 8 · answered Feb 22 '19 at 23:36

I ran into a similar issue. My module level build.gradle reflected configurations specified for "debug" AND "release" accordingly. I was able to successfully run my app on emulator and device (LG) prior To Building and Signing My Release Version Of My App. After Building and Signing The Release Version and attempting to Run The Signed APK on My Phone and Device, i received an Error PM Session 'mobile': Error Launching activity....Error while Launching activity..So I started retracing my steps and realized that before deploying the signed release variant, i opened up the run/debug Configurations Dialog

and mistakenly selected the the Value APK from app bundle value From The Deploy attribute, under the Installation category

I Signed My APK In its ENTIRETY and NOT Via Bundle, so the option selected was attempting to Deploy an invalid App Bundle That Was Never Generated To Begin With, even if it was for the correct Build Variant.

score 1 · Answer 9 · answered Aug 19 '20 at 16:18

1

For me, it was an issue with the gradle version. Make sure your plugin version and the required gradle version fit together, as defined here.

https://developer.android.com/studio/releases/gradle-plugin

You can find out which gradle versions you are using under:

File -> Project Structure... -> Project

answered Aug 19 '20 at 16:18

vorwerg-ni

157
1
5

I got solution after update the gradle version and its plugin version – Farmer May 24 '23 at 11:53

score 1 · Answer 10 · answered Sep 07 '20 at 22:32

1

I tried all the above to no effect. Eventually stumbled across File > Invalidate Caches/Restart... for other reasons and found it worked for me.

answered Sep 07 '20 at 22:32

alman

83
6

score 0 · Answer 11 · answered Jan 08 '18 at 06:37

I have this question too. My solution is checkout to the branch which i had changed the build variants. And at that branch, I can change from release back to debug. Then just checkout to current branch and everything is OK. It seems to be a Android Studio bug.

score 0 · Answer 12 · answered Jun 28 '18 at 08:31

English is not my native language; please excuse typing errors.

I also meet this situation. i do this to solv .
Solv:
1. delete each module's impl suffix type file and build folder;
2. then click this button to sync project with gradle build file. button position

finally. and then this problem will be fix.

score 0 · Answer 13 · edited Nov 17 '18 at 02:02

0

I fixed this issued by:

Add a new build type named debug1 via edit build.gradle;Enable debug function of this build type;
Sync and select the new build type debug1;

edited Nov 17 '18 at 02:02

Stephen Rauch

47,830
31
106
135

answered Nov 17 '18 at 01:33

张坐看云起时

1

But I don't know why I can't to switch to the original debug mode.Anyway,steps above fixed the issue that can't debug. – 张坐看云起时 Nov 17 '18 at 02:27

score 0 · Answer 14 · answered Jun 15 '20 at 16:54

0

This issue seems to occur when opening the project in a symlinked location on linux. Opening the project directly fixed this issue for me.

relevant link: https://issuetracker.google.com/issues/156857164

answered Jun 15 '20 at 16:54

jfaltis

1

While this might answer the question, you should [edit] your answer to include any important content from the link that's relevant to the question in the answer itself. Answers that consist primarily of a link to somewhere else can become invalid if the link stops working for whatever reason. – Hoppeduppeanut Jun 15 '20 at 23:33

score 0 · Answer 15 · answered Nov 11 '20 at 12:15

0

in main root of app in build.gradle

replace it from:

dependencies {
    classpath 'com.android.tools.build:gradle:3.2.1'
}

to my Android Studio v3.0.1 in my case:

dependencies {
    classpath 'com.android.tools.build:gradle:3.0.1'
}

answered Nov 11 '20 at 12:15

saber tabatabaee yazdi

4,404
3
42
58

score 0 · Answer 16 · answered Mar 26 '21 at 21:33

0

March 26, 2021: Would not switch from Release to Debug, File | Invalidate Caches fixed it for me

answered Mar 26 '21 at 21:33

Mick

663
1
9
18

score -3 · Answer 17 · answered Mar 24 '17 at 21:20

Unrelated to your build.gradle file,

Sharing hoping it might help someone else -

I was having similar issue it was because one of the line in build.gradle -

android {
    ...
    publishNonDefault true // remove this line and it should work!
}

Here you can get more detail about publishNonDefualt -

It is also possible to publish all variants of a library. We are planning to allow this while using a normal project-to-project dependency (like shown above), but this is not possible right now due to limitations in Gradle (we are working toward fixing those as well). Publishing of all variants are not enabled by default. The snippet below enables this feature:

I didn't have that line in my build.gradle when I was fasing the issue. — AlexKost, Mar 25 '17 at 02:49
I don't have that line in my build.gradle. What is the relevance? — IgorGanapolsky, May 18 '17 at 16:58

Unable to switch to debug build variant in Android Studio

17 Answers17

Linked