CODEWITHSUNDEEP
android
jcaruso
jcaruso

Reputation: 2494

Signed with a different certificate error but they are using the same keystore

So I had a client come in and give me an app to make a small modification to. However, after i made the modifications and then signed it, using the keystore of the previous developer, it won't upload to the market.

You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s): It then goes to show that the SHA1 are different

Can I not update the app when I have the keystore?

Upvotes: 0

Views: 1142

Answers (2)

Booger
Booger

Reputation: 18725

Looks like you are NOT using the same keystore. You can check this pretty easily using the keystore tool.

Check this SO question: How to check certificate name and alias in keystore files?

There is NO way to update an existing app if the signing certificate doesn't match the original (there is NO way to workaround this)

Upvotes: 1

Jay Snayder
Jay Snayder

Reputation: 4338

You should be able to upload when you have a matching keystore and matching password. If you were trying to upload an application with a different keystore than the original is when you would come into issues.

If the original is lost, then there is no way to update an existing one. You would have to remove the old application and load another one onto the Play Store. Which of course would disrupt current users and cause confusion. As far as I recall that is the resolution in the secondary case.

Upvotes: 0

Related Questions