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. Your app bundle is expected to be signed with the certificate with fingerprint:
SHA1: 46:E8:47:33:68:00:86:A7:E9:EE:59:9C:8A:F1:57:EC:EB:D2:A4:6E
but the certificate used to sign the app bundle that you uploaded has fingerprint:
SHA1: 02:4C:6B:C4:8D:F4:85:61:EF:33:87:AB:71:10:B2:F2:20:69:A1:4B
I COMPRESS MY FLUTTER PROJECT AND THE I EXTRACT AND RE UPLOAD BUT IT DOESINT WORK BUT THE KEY HAS NO CHANGE SAME KEY IS USED BUT I CANT UPLOAD THIS
okay so I faced similar issue when I needed to upload a new update for the app but because the build was from different app it can't be installed on the device, if this is the case with you then the reason is actually two devices have different keystore which makes one app different from other one
You can follow the guide below
https://support.google.com/googleplay/android-developer/answer/9842756?hl=en#zippy=
Hoping this help!
Related
So I just built the new version of my app but when I upload the apk to the google play console I get this error
Image of Error
I have no idea what's causing it. I checked and within unity the key is the same one I used the first time I built the app. ID is same from the keystore. I have no idea what's causing this or how to fix it so i'd appreciate any help!
You must the same signing key used to sign the app bundle when it was initially uploaded to the Google Play Store. This signing key is typically stored in a Keystore file, which you can use to sign the app bundle using the jarsigner tool.
You should use choose the same Project Key Alias of the Keystore.
I am uploading with correct signin key, few time I cleaned with
flutter clean
From android studio - clean project
Invalidate Caches
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. Your app bundle is expected to be signed with the certificate with fingerprint:
/MO2Pu.png
You're signing a newer release with a different key as in regards to an older one. There are only two fixes.
Either find your old keystore and sign this release with it too.
Or contact Playconsole in regards to a forgotten key and the new key that you want to use, this way you'll be able to upload this new one with this new key.
I am using Unity to publish a game and I keep on getting this error when I upload:
You uploaded an APK or Android App Bundle signed with a certificate that is not yet valid. You need to sign your APK or Android App Bundle with a certificate that is currently valid.
I've checked several threads, and the problem they seem to target is the system time and date settings, but I double-checked that and it is correct.
What should I do?
You have to set the correct date and time of his/her system before generating keystore.
You can follow the following thread.
APK signed with a certificate that is not yet valid
The certificate you are signing your APK with has a validity start date past the current date.
Create a new certificate in the same or a new keystore, then update your gradle configuration to point to your newly created key and clean your project before re-creating a new APK (or App Bundle).
I have made an app for the iPhone using flash CS 5.5, tested it on a device (it works fine on there) and I'm member of the development programme. I'm attempting to upload the app to the store after filling in all the information on iTunes connect. However, when I attempt to upload the ipa file through the Application Loader (Version 2.5.2) I keep encountering the same error:
'Application failed code sign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.'
I've tried creating the certificates again but still getting the same error.
Thanks for any help :)
It means that you are not using iPhone Distribution Certificate, which is required to upload apps on the app store. I'm guessing you are using a developer certificate.
Here is link how to create distribution certificate for app store submission: Steps to create a distribtution certificate.
Next time do a search you'll get plenty questions related to this topic. For example:
Application failed codesign verification?
Try again with your release certificates, and make sure that whatever you are quoting there for making the certificate should be same as you app's plist file.
Refer to this links: Building Your App for Distribution
I tried to follow this video to make an ipa
http://www.youtube.com/watch?v=gRhtsnFB0bM
but I have an error when I want to make Product > Archive
[BEROR]Code Sign error: The identity 'iPhone Distribution' doesn't
match any valid certificate/private key pair in the default keychain
It's the first time that I do that so I don't really know how it works, but I think it's a certificate problem. I made the app for someone. I downloaded his certificate from his account in developer.apple.com, what shall I do with it? Shall I make something in xcode to add it?
you need to revoke the previous provisioning profiles in his
account..(if you can get the previous person keychain files ..that
get that and install in your keychain..compiling will be successful)
make a new distribution certificate using keychain in your mac
and then make a new distribution profile using that distribution
certificate..then you will be able to compile using that profile.
I get this error all the time since I use the same scheme for testing as I do for distro. You will have to go into your build settings for the project and the target and set the code signing back to iPhone Developer. Clean your settings and rebuild. That should do the trick.