Recently, I've updated Android bundle id. Is it required to generate a new release keystore file after that?
The main concern is that Google Sign In no longer works with the following error: DEVELOPER_ERROR. The app is already available in stores and issue is reproducible only after downloading a build from it. Works perfectly locally.
Thanks!
Related
I am trying to upload a new version of our app (first time being exposed to android) and am dealing with this error when trying to upload the .aab file. I assume it means I don't have the original signing key file, I do not have access to it either, how can I get past this to upload?
You should find the old version of app and keyStore file that was first uploaded with your previous update, if you create and upload new keystore google will always prompt with this error, i hope you find the old keystore file used for previous version update
It's been a while since I submitted an app to google play, but when I recently tried, I got the following signing error:
You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in Play App Signing, you should sign your APK or Android App Bundle with a new key before you upload it.
I have created my build with
% ./gradlew assembleRelease
as I always have.
I am not aware that I have changed anything signing-related on my system since my last successful upload.
What has changed is:
Android Studio Version
Google play looks different
What I have tried:
verified the debuggable is not set and thus defaults to false
ran ./gradlew clean first
I have tried to to find this particular error on the web but to no avail.
What am I doing wrong?
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.
Hello all I have an APP on play store and I uploaded the bundle file first time and kept the keystore save it and then uploaded to playstore. After some time I updated the APP with version 2 and used the keystore app signing key which I created in the first time it got uploaded
But now I am doing the same and the playstore say
your Android App Bundle is signed with the wrong key. Ensure that your
app bundle is signed with the correct signing key and try again
I don't know what to do here, its so bad I am stuck here This is my first APP and I already have this signing issue can you suggest me how to upload the new versions of APP on playstore and fix this signing key issue.
Check for the key store you use with the app is correct and no changes made on it.Try again.And also ensure that the key store you are using is of the same app not of any other app.
There a different approaches to overcome this problem. See also the link code4rox provided though nothing of these proposals worked for me and I wasted many days and nerves. My suggestion to you would be:
Reset the old keystore with the support of Google Play Developer Support (Play Console)
Create a new keystore with your IDE
Convert the new keystore to a .pem file with JDK's command line tool "keytool" or use "KeyStore Explorer" (open source GUI replacement for the Java command-line utilities keytool and jarsigner)
Send the .pem file to Google Play Developer Support.
Two days later you can update your App with the new keystore.
We have recently purchased a game from another company and have done some updates to it with all the information converted over to our side.
The game is made and updated using Unity and is for the Android platform.
After doing all of these updates in Unity and using the Keystore that they supplied us (along with the passwords for the Keystore and the Key), we built the APK with no errors.
When I go into the Google Developer account and try to upload the new APK for testing, I get an error at the end of the upload that tells me that the certificate used in the APK is different than the one originally used on the other APKs so it can not upload the APK.
I have searched everywhere and people are saying that it is the Keystore and the key but I have the correct Keystore and Key because Unity would not allow me to build outside of debug testing without it (I tested this by putting a wrong password in for the Key and Unity gave me errors saying I had the wrong password).
I am using
- Macbook Pro with OSX 10.8.3
- Unity Version 4.1.3
I have all the correct SDKs for Android and the manifest package name matches the Bundle Identifier for the project. (The Bundle Identifier also matches the correct one attached to the Google Dev site.
Please help.
Unity will not stop you from building out an APK signed with a keystore that is different that what a previously built APK was signed with. So the unfortunate truth is that the version currently on Google Play was indeed signed with a different keystore. I've run into this problem myself in the past.
If you don't find the keystore that the app was originally signed with, you will need to pull down the current app and upload a new app.
I try to follow the practice of making the sure the production keystore is stored within the project's repository in an easy-to-find location.