Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Gradle signing app with packageRelease “specified for property 'signingConfig.storeFile' does not exist”

Tags:

I am trying to test an app with Build Variant in release mode in Android Studio with a project using Gradle.

build.gradle:

(omitted dependencies and repositories)

android {
    apply plugin: 'android'
    compileSdkVersion 19
    buildToolsVersion "19.0.0"

    defaultConfig {
        minSdkVersion 11
        targetSdkVersion 16
        versionCode 1
        versionName "1.0"
    }

    signingConfigs {
        release {
            storeFile file("release.jks")
            storePassword "password"
            keyAlias "MobileAndroid"
            keyPassword "password"
        }
    }

    buildTypes {
        release {
            runProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
            signingConfig signingConfigs.release
        }
    }
}

If the Build Variant is release Gradle returns an error

A problem was found with the configuration of task ':app:packageRelease'.

File '/Users/andre/workspace/MobileAndroid/app/release.jks' specified for property 'signingConfig.storeFile' does not exist.

Removing "signingConfig.storeFile" returns an Android Studio message box error:

Application Installation Failed

Installation failed since the APK was either not signed, or signed incorrectly. If this is a Gradle-based project, then make sure the signing configuration is specified in the Gradle build script.

release.jks exists and using the Android Studio wizard "Build > Generate Signed APK..." I can generate an app.apk signed.

How do I solve this error in Gradle?

like image 387
André Ricardo Avatar asked Feb 14 '14 13:02

André Ricardo


2 Answers

Please double-check that the file exists at the place the error message is looking (Users/andre/workspace/MobileAndroid/app/release.jks) and that there are no permissions problems preventing the files from being read.

like image 88
Scott Barta Avatar answered Sep 21 '22 22:09

Scott Barta


For me it was because i was entering in just the name of the key when it was asking for the full path.

enter image description here

like image 43
j2emanue Avatar answered Sep 21 '22 22:09

j2emanue