简体   繁体   中英

How to debug the Android App in release mode using Android studio

For some reason I have to run my Android App in release mode.I have to run through the code when running the app just like we use in debug mode. My break points are not hitting when I run in release mode, I have added android:debuggable="true" in manifest. Still the breakpoint is not hitting. Any help.

Thanks in Advance

In your gradle file, you must add debuggable ability in your release flavor.

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

signingConfig is release configuration it must be added in gradle file in android{} block, something like this:

signingConfigs {
    release {
        keyAlias 'YourAppKey'
        keyPassword 'somePassword'
        storeFile file('appkeyfile.jks')
        storePassword 'somePassword'
    }
} 

In my case, I have created the debug configuration same as previous release build and started debugging. It means you have to give sign build in debug version also in build gradle.

signingConfigs {
    config {
        keyAlias 'abc'
        keyPassword 'xyz'
        storeFile file('<<KEYSTORE-PATH>>.keystore')
        storePassword 'password'
    }
}
buildTypes {
  debug {
      debuggable true
      signingConfig signingConfigs.config
      proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
    }
}

So It will have the same sign as release build and you can debug when it runs.

 buildTypes {
    release {
    debuggable true
    minifyEnabled true
    proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
}
}

happy coding.Mark this answer up..if it helps.. :)

Few pennys for the new comers.

If even After adding debuggable true in release block, your debug points are not hit.

Remove the following code from the release block.

    minifyEnabled true 
    shrinkResources true //remove resources
    proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

There's no "release mode". What you refer to is the build type which means steps taken during building (like minifying etc). Setting android:debuggable="true" will not automagically help, because when you "Run" the app instead of "Debug" you do not connect debugger to it so it will not stop for that particular reason.

So you can set up your debug build to be produced the same way release is, but is quite unclear what is the reasoning behind your need and I got a feeling you are trying to go the wrong way (ie debug is usually not using ProGuard, while release build is and ProGuard changes the resulting binary so your breakpoints from source will not really work anyway).

I think Marcin's argument above makes sense (much as there are situations that require debugging release builds), so here is a slight variation of the accepted answers that worked for me:

android {
    ...
    buildTypes {
        release {
            shrinkResources false # this was key
            minifyEnabled false # seems that it can't be set to true if shrinkResources is false
            proguardFiles getDefaultProguardFile('proguard-android.txt'),
                    'proguard-rules.pro'
        }
    }
}

Adapted from the official docs

NOTE:

When I set minifyEnabled true , the following crash occurred on app launch:

java.lang.RuntimeException: Unable to instantiate application co.mycompany.app.MyApp: java.lang.ClassNotFoundException: Didn't find class "co.mycompany.app.MyApp" on path: DexPathList...

In 2022, or at least in MY case

I tried many solutions but didnt work finally solution was to create a new siginig key and use it with all build types &variants.

Steps

1 - Go to AndroidStudio top menu select Build>Generate Signed Bundle /APK > (choose APK )

*for the first time create a new key (you know how to create one? or read docs )

BUT NOTE while you are creating key choose build type debug then continue

2 - Again Go to AndroidStudio top menu select Build > Generate Signed Bundle /APK > (choose APK) BUT this time choose existing key ( the one we made in previouse step)

in previouse step we chose build type debug this time choose release and continue..

3 - Repeat steps 1 & 2, with AAB (release & debug)

this is basically making sure all build types are being signed using same configs.

NOTE

maybe you need to add below code to app build.gradle

android {

    ...

    signingConfigs { <-- Add this
        config {
            storeFile file('PATH_TO_KEY.jks')
            storePassword 'YOUR PASSWORD'
            keyAlias 'YOUR KEY ALIAS'
            keyPassword 'YOUR PASSWORD'
        }
    }

   ... 


   buildTypes {

        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'

            signingConfig signingConfigs.config <-- this
        }

        debug {
            signingConfig signingConfigs.config <-- this
        }
    }

}

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM