您上传了在调试模式下签名的 APK。 您需要在发布模式错误中签署您的 APK

Question

I am trying to upload an Application on the Google Play store. I am building the .apk and signing it using Maven. I have used maven-jarsigner-plugin to sign the .apk file. I am using the key that I created using Eclipse wizard for signing another Android app. I zipalign the .apk file using the following command: zipalign [-f] [-v] infile.apk outfile.apk

When I try to uplaod the application on the playstore, I get the error You uploaded an APK that was signed in debug mode. You need to sign your APK in release mode. Can anyone please tell me how to sign the apk in release mode? I am new to Maven (started using it today). Thanks

Answer 1

Change to: signingConfig signingConfigs.release

from signingConfig signingConfigs.debug

in your build.gradle app level

Answer 2

I don't know how you do that in Maven, but you need to compile your app with a release keystore. You can create one with keytool , which is available in your Java bin folder:

$ keytool -genkey -v -keystore my-release-key.keystore
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000

When creating it, you must supply two passwords, one for the keystore and one for the key. When your keystore is created, you can use the Eclipse Export wizard to compile your app in release mode.

For further details, please refer to http://developer.android.com/tools/publishing/app-signing.html#releasemode

Answer 3

Always create your keystore with name and alias containing "release" not "debug". If you are having the "You uploaded an APK that was signed in debug mode. You need to sign your APK in release mode error" it's certain that you are using default keystore which is 'debug.keystore' hence generating apk in debug mode.

Solution

1. Generate new keystore
2. Give reference in build.gradle file
3. Change build variant to 'release'
4. Build

this should fix the issue.

Answer 4

Go to android/app/build.gradle

At the end of the file:

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug <==== change this to release
    }
}

Resul should be like:

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.release
    }
}

Answer 5

I had the same issue with my flutter app,

Add these to your android/app/build. Gradle:

before android { compileSdkVersion 30

def keystoreProperties = new Properties()
def keystorePropertiesFile = rootProject.file('key.properties')
if (keystorePropertiesFile.exists()) {
keystoreProperties.load(new FileInputStream(keystorePropertiesFile))
}

And after defaultConfig {

}
signingConfigs {
    release {
        keyAlias keystoreProperties['keyAlias']
        keyPassword keystoreProperties['keyPassword']
        storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null
        storePassword keystoreProperties['storePassword']
    }
}
buildTypes {
    release {
        signingConfig signingConfigs.release
    }
}

Answer 6

For flutter error, By default flutter creates buildtypes like below

  buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

you should change the signingconfig line

        signingConfig signingConfigs.release

Answer 7

Using -genkeypair instead of -genkey solved the problem for me.

So: keytool -genkeypair -keystore name.keystore -alias nameapp -keyalg RSA