I am getting this error while i try to run my project from Android Studio to Genemotion. It was working perfectly fine and then I signed the app to test it on other phones and ever since I am unable to run it from android studio. No idea what to do, I tried messing around with Gradle Tasks but they didn't workout.
I have already seen other posts like these Getting error :app-release-unsigned.apk is not signed but they didn't help
I you don't want to add the to your Gradle file the signing information, you can just change to the debug mode for your current build type:
If you want to add the signing information to your build.gradle just do the following:
signingConfigs {
release {
storeFile file("release.keystore")
storePassword "******"
keyAlias "******"
keyPassword "******"
}
}
Related
I have installed previous version of my app from Google Play Store.
Now, I make an apk release with the same keystore file with gradlew assembleRelease command or with android studio, and try to install it manually in device or with gradlew installRelease on emulator.
But every time I got App not installed error.
I got this on LOGCAT:
INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.myapp.myapp signatures do not match previously installed version; ignoring!
I use enableSeparateBuildPerCPUArchitecture in my gradle file.
and also I enable v2 signing with these commands in gradle file (in release section of signingConfigs):
signingConfigs {
debug {
storeFile file(...)
storePassword ...
keyAlias ...
keyPassword ...
}
release {
storeFile file(...)
storePassword ...
keyAlias ...
keyPassword ...
v1SigningEnabled true
v2SigningEnabled true
}
}
NOTE: Also if I install the previous version of my app manually, the Play Store won't update it.
This is the expected behaviour.
This is because the keystore signatures don't match, as most likely you have opted in for your signing key to be managed by Google. You will have to uninstall the previous app before installing the new version if it comes from a different source (Google Play/ Android Studio build).
I read many similar content but I couldn't find a solution.
I am a flutter developer, yesterday i signed an android application and sent it to google play.
I cannot find the key file I created or I am not sure if its name is the key.
I created it yesterday on this mac computer , but today there is no such file. I only have a file named 'private_key.pepk' on my desktop.
Can I find out where the path I chose when signing for the first time from my Android project? i need your help
Android developer that hasn't signed a Flutter app yet, but in build.gradle you should have something like this:
signingConfigs {
release {
storeFile file("EITHER A PATH OR RELATIVE PATH")
storePassword sPassword
keyAlias kAlias
keyPassword kPassword
}
}
I made this Android app that fetches some data using AI Platform Training & Prediction API from Google Cloud Platform. For this app to work it needs to be approved by GCP using SHA-1 Fingerprint certificate. I am making this app as an assessment for module Im taking at the university, so, when the teacher will open my Android Studio project it will have a different SHA-1, so the app will not fetch the data...
Any Ideas how I might be able to maybe set a permanent SHA-1 key for my project, so when the teacher will open the project, Android Studio will not generate a new one?
Thank you!
The SHA-1 is based on the app signature. Since this is for a project I suggest you do the following (never do this in a production app).
Create a new signing key (Build -> Generate Signed Apk -> APK ->
Create New)
Move the signing key to your project's folder
Add this to your app.gradle
android {
signingConfigs {
debug{
storeFile file("your_key.keystore")
storePassword 'password'
keyAlias 'alias'
keyPassword 'password'
}
release {
storeFile file("your_key.keystore")
storePassword 'password'
keyAlias 'alias'
keyPassword 'password'
}
}
}
EDIT: Forgot to mention, run the signingReport gradle task after you do this to get your new SHA-1 that you have to add to your project.
after creating the .keystore file and running the report I get the new SHA-1 key, but the build fails. I get this:
Entry name 'play-services-ads-identifier.properties' collided
I can't find any reason why the store doesn't accept any apks on new apps and others, it every time return please upload another apk
1.0, app code 1 brand new app returns same error with 2 different dev accounts on 4 different vpn(Netherlands/germanmy/singapur..) and 2 different browsers?(opera/safari) also I have deleted cookies etc
my signin in that project is react native
signingConfigs {
release {
storeFile file("key.jks")
storePassword "dosa"
keyAlias "dsa"
keyPassword "dsa"
v2SigningEnabled true
}
}
You will have to set
android:debuggable="false"
in application tag of the manifest file. This is important for uploading your apk.
and if this already set properly and Google Playstore still rejects your APK, then modify your build.gradle
signingConfigs {
debug {
storeFile file("my-keystore-file.jks")
storePassword "my-password"
keyAlias "my-alias"
keyPassword "my-password"
}
}
This will set your own key for debugging.
If your problem still exists then I would suggest reading the documentation, you can read it here it's given properly.
1.0, app code 1 brand new app returns same error with 2 different dev accounts on 4 different vpn(Netherlands/germanmy/singapur..) and 2
different browsers?(opera/safari) also I have deleted cookies etc
I tried with Firefox and it worked thanks...
I've been developing my project in Eclipse IDE. The app is submitted on Play Store, and I've published a couple of versions updates successfully.
Recently I've migrated to Android Studio (and gradle, of course). I've done some changes to the project code base, including min and target sdk changes, but package name remains the same. The project is successfully compiled and debug app is successfully assembled and running ok.
But now I can not assemble a release version because of :
Keystore was tampered with, or password was incorrect
The keystore have not changed, and I do know it's password.
I've set signingconfigs in build.gradle:
android {
...
signingConfigs {
release {
storeFile file("keystore/motolife.keystore")
storePassword "***"
keyAlias "motolife"
keyPassword "***"
}
}
buildTypes {
release {
signingConfig signingConfigs.release
}
}
...
}
I've tried also to sign using jarsigner:
jarsigner -verbose -keystore keystore/motolife.keystore build/outputs/apk/motolife-new-debug.apk motolife
But no luck.
I've even installed gradle support for Eclipse and tried to assemble signed release app , but got the same "Keystore was tampered with, or password was incorrect" error.
try doing something like this then:
release {
storeFile file("keystoreName.keystore") //change value per signing
def pass = System.console().readPassword("\nPlease enter key password: ")
pass = new String(pass)
storePassword pass
keyAlias "revision3" //need to change these values per signing
keyPassword pass
}