I generate apk - not crosswalk - but upon submit second version to Play getting:You must use the same certificate.
Upload failed
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):
[ SHA1: .................. ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: ....................]
what's the solution...? I changed PC OS and XDK version but - OS change is prior 1st submission....I think.
連結已複製
Hello,
The package name must be the same and the .apk must be signed with the same private key. If the package name and signing certificate do not match those of the existing version, Market will consider it a new application and will not offer it to users as an update.
The package name must be the same and the .apk must be signed with the same private key
PACKAGE NAME Is same.
I do Not remember used private key - or changed it... How is relates private key to my project and where found??
App version code: 1 // this should be constant equal to one??? I used 2 in second version...
@Leonidas -- How did you build the app that is now in the store? Using the legacy APK build? Or did you build using some other system? In the XDK, the build certificate is automatically generated for you, based on your userid and account. If you changed accounts you will get a new certificate, which does not match the original certificate.
Does not matter if you changed from 3.5 to 4.1.
It's possible you have two accounts as a result of the transfer to our new login system. There were some situations where that happened. I'll ask the appropriate engineer if they can help.
