CODEWITHSUNDEEP
androiduploadgoogle-playapk
RushDroid
RushDroid

Reputation: 1600

You uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play-Upload apk to google play

I Want to upload my apk to google play store.but its Show me error like this.

**You uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play**

and than i searched for this and i receive suggetion to change the android:debuggable="false" in manifast.xml.

I changed like this

manifast.xml

 <application
    android:allowBackup="true"
    android:debuggable="false"
    android:icon="@mipmap/ic_launcher"
    android:label="Concall"
    android:screenOrientation="portrait"
    android:theme="@style/AppTheme" >

and in my build.grable(Module)

android {
buildTypes {
    debug {
        debuggable false
    }
}

1.is the enough for upload Apk to google play store?

2.if i pick up apk from my project folder(app>>build>>output>>apk>>apk-debug.apk) after this change than after it will able to upload in google play store??

Upvotes: 35

Views: 57581

Answers (8)

Hari Agus W
Hari Agus W

Reputation: 91

Maybe you add set debuggable="true" . you can remove code that or set to false

If you not find in build.gradle you can check in AndroidManifest

Upvotes: 0

Amit Gupta
Amit Gupta

Reputation: 105

This feature can be controlled from the manifest file also, disable from there

android:debuggable="false

Upvotes: 2

Jacksonsox
Jacksonsox

Reputation: 1233

I was getting this warning when I wasn't selecting the "Signed" version.In the signed version, select release to deploy.

Non-signed "Debug" version vs. Signed version.

Upvotes: 0

yogikalwar
yogikalwar

Reputation: 81

This should be the flags for uploading the Apk to Playstore. Not needed to be release build. If you want to test your qa build, you can do ./gradlew assembleQa with flags

minifyEnabled true
debuggable false
shrinkResources true
testCoverageEnabled = false

Upvotes: 1

Rahul Chaurasia
Rahul Chaurasia

Reputation: 1641

In my build.gradle file, I had debuggable = false and I was wondering why I'm getting this issue. later I found that it was debuggable = true in my AndroidManifest.xml file's application tag

Upvotes: 11

Raja Jawahar
Raja Jawahar

Reputation: 6972

I was having the same problem. Unknowingly I kept

debuggable true in release buildType

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

        }
    }

After changed to false. Its working fine.

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

        }
    }

Upvotes: 8

dsrees
dsrees

Reputation: 6286

I ran into this error and my application did not reference debuggable anywhere. After a little bit of searching, I found that I accidentally had testCoverageEnabled true in my release build type.

release {
    testCoverageEnabled true
    ...
}

Removing this resolved the issue.

Upvotes: 15

niqueco
niqueco

Reputation: 2408

Don't use the debug variant output! Build a release apk. You can do that in Android Studio by going to the menu Build -> Generate Signed APK. Or by executing ./gradlew assembleRelease if you have properly configured signing in the build file.

Upvotes: 26

Related Questions