I use Android Studio: Arctic Fox 2020.3.1 Canary 12
I have a strange problem. I have key store, and I enter correct passords and alias and set "Remember passwords" as On. For the first time, everything is fine. But if I reuse Generate Signed Bundle, my key password has a different meaning and I have error:
> Task :app:packageRelease FAILED
Execution failed for task ':app:packageRelease'.
> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
> com.android.ide.common.signing.KeytoolException: Failed to read key profit from store "D:\android_profit_key": Cannot recover key
And if I enter correct key password again - the error will disappear and the build will end.
Perhaps this is important:
My key was created on the Mac OS system. But now I use Windows 10.
Maybe now I must use Same passwords in key store and key password (Now they are different from each other.)
I noticed the following pattern:
When I decided to create a new key with different passwords I got two errors:
Thus, now the android studio does not start working correctly if the passwords are different.
Decision:
Create a new key or add an alias with the same password as the key itself.
Related
For some stupid reason android studio decided to start failing generating signed APK always if I dont manually enter the password each time. now it just started happening around maRCH-june this year(cant remember exactly when), until then I always just pressed next->next->finish cause i ticked the Remember passwords checkbox and everything worked great, but suddenly it started failing.
I tried generating once without checkbox and then generatin again with it
I even tried on a different computer but it still happens
If i dont enter the password manually each generation and rely on the remembered password it will always fail, even if the last generation I enetered the correct password and it generated successfuly, meanwhile entering the password each time works aslong as the password is right(like it should)
anyone knows how to fix this problem? while not stopping me from generating signed APK its annoying as hell
In my case it was caused by Windows 10 Controlled folder access. Try adding folder with the encryption key file to exceptions list or turn Controlled folder access entirely off.
I am trying to verify the integrity of Putty msi from their website ( not to say I don't trust it. Instead, just use it as a case study ).
On the website https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html, there are signature (.gpg file) and public key (.asc file) for release package.
But what tool is available on Windows 10 to sign the msi using their own public key to generate a signature, then compare the generated signature against the one published on their websit.
I was trying to use Kleopatra. Which I just installed last night and generated a pair of keys for myself. Thus I am a bit struggling at how to instruct Kleopatra to sign the putty msi binary using their public key. ( I don't see the option to remove it).
It would be great if someone could point me a right direction or better tool.
Thanks,
Frank
I've been trying to build a new version of my app bundle and it won't build it with the same key.
I click on Build>Generate Signed Bundle or APK...>select Android App Bundle>click Next, then I select my key, I put the same key store password, the same key alias, check for the key store path twice just in case, click on Next>select release>Finish and nothing happens. I don't get an error or any kind of prompt, just nothing.
How do I fix this?
edit: I found the answer, the alias wasn't the same, Android Studio won't even try to build a new version if the key alias is different
Had to uncheck the "Export Encrypted key...." option.
What worked for me was removing .keystore suffix from key path
I'm using SHA1 debugging key in firebase for debugging my application, but I want to release my app in the play store where I'm providing Google authentication in my application.
What can I do for release mode where do I get SHA1 release mode certificate and what can I do with that?
Is it necessary to download the json file again? How can I do that?
I had the same problem and found this enter link description here
Basiclly what he did, and for me works fine, is one you upload the app to google play:
Go to Release Management
Select App Signing
Use the SHA1 that you see there in FireBase
The app bundle was generated by the first PC (Ubuntu 18.04) using keystore and its password. Google Play accepted app bundle and application was updated successfully.
After that same process was repeated in another PC (same project, same keystore, same password) and successfully generated app bundle. But Google Play did not accept it and showing error:
App bundle was signed with wrong key. Choose appropriate key: SHA1: C9:AF....
I tried different ways to solve this problem:
Tried to create app bundle on Windows and MacOS machine. Could not try on Linux machine because there are no Linux machine available
Besides the app bundle trying to create the apk which was generated successfully, but when uploading Google Play showed error: signature is invalid
Developer who owns Linux machine is leaving project and we need to generate app bundle in another machine.
What is the reason for this problem if app bundle is created by same keystore and password? How can I solve this problem?
I'm pretty sure even though you think it is being signed with the same keystore, you have made a mistake somewhere. You can check this for yourself though. App Bundles are just signed using the same scheme as jarsigner. So you can print them using keytool.
keytool -list -printcert -jarfile mybundle
If the values are the same for the bundles produced on both PCs then they are signed with the same key in the same keystore. Otherwise you are doing something wrong. Maybe using a release key on one, and a debug key on another, or the keystore has two different keys with different names. Or maybe you think you are using the keystore when you aren't.
Google play accept the apk generated by same keystore file. So please check you have made some mistake. Use the previous keystore and compare it with the current one to check and verify the SHA! and SHA256 Signature
if upload an Application on play-store with one Keystore you don't need to create another keystore for the same project, just use the same keystore for your next version uploading.
NOTE: Google not allow to create multiple keystore for same project.
Remember the selection of signature of version what you selected. this must be the same for your next release.