I've been learning programming on Android Studio and already have an app about to publish. Some points are missing for trying to learn by myself and my question may sound silly.
3-4 months ago I generated my first signed apk. Since then as I developed my app, sometimes I generated apks to test my app. When I was generating signed apks keystore file (jks) path
was remembered and I quickly click forward button to generate signed apk. The location of my jks file was "C:\Users\Me\AndroidStudioProjects\MyApp\feature\build\outputs". After Android Studio update I can not generate signed apk with this key. Whatever I do, they all end with "No key with alias '....' found in keystore C:\Users\Me\Desktop\"
Keystore path is always seems as desktop. I can not change it. When generating apk I already select my existing keystore path but Android Studio always looks for keystore file on desktop.
Another problem is alias name mentioned in the error message is different my existing alias name. Android Studio looks wrong place and wrong alias name. So why is Android Studio acting like this? How can I generate a signed apk again?
Related
I've changed my pc and reinstalled Android Studio as well as my old project.
I've copied my old keystore files in the following directory
"C:\Users\MyUserName.android"
But when I run the program it looks like the keystore is not recognized(not connecting to google services and so forth...)
How do I check if my keystore file is working properly?
There are two keystore files usually used. One for debugging and one for doing release builds of your apps you plan to upload to an app store. The debugging keystores can be generated anytime, so, it doesn't hurt to create a new one in your new IDE setup. But for your release keystore, you will want to build a new version release of your app and export it, then try to upload it to your App Store. If there is anything wrong with the signing, the App Store should reject it.
Just try to generate signed apk . If you got error than you keystore is not setup. If it generate then it's okk.
I recently made my first app in Android Studio and made it into an APK. Google play said I had the wrong signature for the APK but I don't know how to change the APK with different signatures nor revert the program back in order to manually change it inside Android Studio. Any help on this?
Here is step by step what I did to get to this point. I finished writing my program and went to "build" then "generate signed apks" where I went through the process of making the keys, key store etc. At this point everything is fine. I just need to somehow go back into the apk and either change the signatures of it or unpack the apk in studio and redo the process of generating signed apks.
You need to sign the apk with the same public-key certificate which you use in the previous uploaded apk. When you build the release apk via Build -> Generate Signed Apk.., you will be presented with the following dialog:
Then you must use the same certificate file (something like android.jks) for the Key store path.
The documentation says:
Every app must use the same certificate throughout its lifespan in
order for users to be able to install new versions as updates to the
app. For more about the benefits of using the same certificate for all
your apps throughout their lifespans, see Signing Considerations
below.
So, if you lose the certificate file, there is no way you can upload the apk with the same package name again. It will lose forever, gone. You also can't delete the published apk to reuse the same package name again.
I'll try my best to convey what my problem is, but I am having issues updating a clients application that is currently in the Play Store. The old version of the app was created by different developers.
The previous version of the app by the looks of things was created using Adobde Air, I don't have any experience at all with Adobe Air, so not too sure about the signing process with the APKs.
My new version is a new project (with same package name) created in Android Studio.
I obviously need to sign the release APK with the same certificate as the previous version. Can I do this via Android Studio using the Build > Generate Signed APK?
Will the previous developers have to provide a .keystore or .jks file? as I said i'm not sure how the signing process works when using Adobe Air.
Any help would be appreciated.
Thanks.
If you can build an apk and have the original keystore file you can sign it via the command line.
Take a look here:
You uploaded an APK that is not zip aligned error
You'll need to do the jarsigner step first, then the zipalign on the resulting file. 4 works for me as the alignment value.
I have created cordova App using Visual Studio 2015.
If I build App in Release mode unsigned APK created.
Now I want to deploy the App.
How can I create keystore?
How can I sign my apk created in Released folder?
Note: I dont have android studio
I followed MS instructions from here, see section Package and Sign Android app (shown below), and it worked for me.
To sign an Android app for distribution
1.Generate a keystore and provide the information required to create a certificate (private key). For more information, see Signing your applications in the Android documentation.
2.When you have created a keystore, open the res\native\android folder.
3.Open the ant.properties file, and enter information about the keystore and the alias.
The Key.store property in ant.properties must specify a relative or absolute path to the certificate file.
4.Put the keystore you created either in the same folder as ant.properties, or in some other location. (For example, for security reasons, you might not want to check the keystore into source control.)
5.Build the Android app.
When you build the app, Visual Studio will sign the package with the credentials you supplied.
I am creating an in-app purchase app. I have uploaded apk file once while creating the application in Google Play developer console. But now when I am trying to upload another version of apk file it is showing error of different SHA-1 keys. I have changed the version code and package name is also same. I referred questions here and I got to know that apk should be signed with same certificate.
But my problem is when I export the project from Eclipse to generate signed apk it is not allowing to use existing keystore; moreover when I select existing keystore the dropdown list of alias are empty. So each time I have to create new keystore. Also it is showing "Invalid keystore format" on selecting exiting keystore. Please provide me with some solution to how can I generate an APK with same SHA-1 key.
Is this apk file generated from another computer than the first?
Make sure to have the same .keyStore file on your different PC.