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.
Related
Recently trying to create a new App and upload a brand new APK with self signed certificate (Not Google App Signing) Results in the following error
You uploaded an APK or Android App Bundle that is signed with a restricted certificate. You need to upload an APK or Android App Bundle signed with your own certificate.
I don't believe this error is entirely correct as I do sign the certificate myself locally, this seems like a recent change to our on boarding process and opt-in is now default for google app signing but our infrastructure doesn't have the right pipeline for this yet.
Is there any other things to verify and test, as I see the keystone file is still there and there's no build errors when it's being signed. Also this is a brand NEW application I don't understand why this error would occur for the initial upload since there's no other keys to check against.
I've searched the net but most issues appear to be happening in 2018 and this is more of a recent change that started to occur for us.
EDIT: This is using Cordova build tools not through Android Studio.
Try to follow these trouble shoot steps and see if that will solve your issue:
Clear everything in the Release folder, present in app->build->outputs->apk->release.
Generate new signed apk which will get created in the same above mentioned directory.
Make sure you are bumping the version code.
I don't have a full answer as to Why it was failing, however right after the build for cordova build android --release that APK will upload. But If I use that APK in an emulator to test something first that APK is no longer valid to upload and I get the error pasted above.
basically in our pipeline I had to create a copy of the APK right before creating screenshots and then use the copied APK to upload onto google console.
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?
What's The matter
I built a debug APK and share it to client by downloadable link. Few days back, I formatted my PC. Now again I gave an update to client for existing APK. When client tries to update (without uninstalling older one), app shows Android App Not Install.
I would like to know, do the Signature of APK before and after formatting PC will be different?
If 'YES',
What are the possible solutions for updating newer APK on
older(installed) one?
If 'NO',
Why I am getting, Android App Not Install. An existing package by the
same name with a conflicting signature is already installed
I would like to know, do the Signature of APK before and after
formatting PC will be different?
Yes, if you are using default debug keystore. This is normally the case if you are building your apk through Android Studio. This keystore will be deleted after you have formatted the PC. A new keystore will be created after you install the Android-Studio
No, if you maintain your keystore seprately and use it consistantly to sign your app before release
Solutions
If you have used debug keystore then only solution is to uninstall your previous app and install a new one
If you have just missed the signing configuration, then simply create a new APK signed with correct keystore.
Checkout my answer in this post if you want to ensure that in future, all your dev workstation should produce debug apps signed with same keystore, even if you format your PC.
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 recently uploaded my game on playstore made with unity but I forgot the password to the keystore when I tried to build an update.
After hours of googling I've learned the importance of the keystore file. After a few trial and error attempts I finally figured out the correct password.
However, what if in the future my keystore.debug file gets deleted accidentally? Will it be generated automatically again by unity or do I need to make a backup for this file on the cloud?
If I need to make a backup than do I need to backup only "user/.android/debug.keystore", or are there other files I need to backup as well?
Some exaplanation:
debug.keystore (located on user/.android/debug.keystore) as the name implies, it is only used for debugging. That means, it's only used when you're sitting on your computer with the phone connected via ADB and typing code.
When developers release an app. Another keystore is used, the "release" keystore. That is the one you selected when clicking "Generate signed APK" or set on your gradle file, that you had to create a password for it. That file can be located anywhere on your system, you created it, you should know where it is. That one is very important. That one is the one that will allow you to update the app on the Play Store.
Direct answers:
debug.keystore is disposable and you don't have to worry with it.
the keystore used when exporting the .apk file, that one is VERY VERY important and YES, make backup of it everywhere you can! On an external hard-drive on your house, on a USB-drive and at least 1 cloud backup (e.g. Google Drive). If you loose that file or the password, you won't be able to update your app again.
I hope it helps.
You have to differentiate between debug.keystore & release keystore
debug.keystore Android User Guide
When running or debugging your project from the IDE, Android Studio automatically signs your APK with a debug certificate generated by the Android SDK tools. The first time you run or debug your project in Android Studio, the IDE automatically creates the debug keystore and certificate in $HOME/.android/debug.keystore, and sets the keystore and key passwords.
No need to remember as its generated automatically
release.keystore
Needed to publish on google play console, But take care after you generate it and used to release signed version for push to production when you app become published you can only send updates using this key. it will be permanent for you app package name on Google play. You have to backup key and it's protection password too.