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
Related
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.
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.
In the new version android studio(3.2), how do I get the apk file(I do not want .aab) for publish? I want to publish my application in a store other than Google, but only the apk file can be released. Please help. I do not know English well. I’m sorry if something I wrote wrong
Within the "Build" menu there is a submenu "Build Bundle(s) / APK(s)". There you can just select "Build APK(s)". The resulting file will be saved in app/build/outputs/apk.
Alternatively you can use the "Generated signed Bundle/APK" wizard which can found be found in the "Build" menu as well. Just select the lower option ("APK").
You can upload anything to Google playstore either bundle or apk
see this to know more about bundle
click on build ,
then on generate signed bunde/ apk
when the popup appear select apk(at bootom)
click next
choose key store path or create new
click next
On signature version checked both the option
click finish
on event log you will see message of creation and path where it has created
I have an app on the google play store that's getting around 3k downloads a day. Recently I tried sharing my files through google drive and they all got screwed up and won't work in Android Studio when I open them. Is it possible for me to start from scratch and submit that update to the listing I already have? All I'd like to do is place some ads into the app
I still have the key for the file I believe.
Thanks for any help in advance!
You can still sign a new version of the app so long as you have the original key and passcode (if you used one).
Submitting successfully will also require you to have the same package name and a version number higher than your last release.
Was able to find the answer! Turns out I can create a new android studio project with the same package names and sign with the old key.
I have an installer which needs to add a key to Currentuser under \Software\Microsoft\Office\12.0\Excel\Options. It must be CurrentUser because excel does not look in LocalMachine. I have a customer that requires Admin rights for an install. I found that when the installer was run as the Admin user, the key was created under the Admin users registry settings. To get around this, I wrote a custom action which created the Excel key in Currentuser, and then copied the key to every other user currently logged on to the machine. This seems to work.
The problem i now have is on the uninstall. The registry key is left in place, which causes issues with Excel. What is the best way to get rid of this registry key on an uninstall?
I am using the Windows installer in VS 2010.
Currie
try installing and running Revo Uninstaller. Once it's installed, see if excel is still there to be uninstalled. In REVO, there is a step in the uninstall process where you check the checkboxes, in bold text, of the registry items to be deleted.
http://www.bleepingcomputer.com/download/revo-uninstaller/
(on the site, click "download Now" instead of the "download" button at the top (which is just a link to google leads).