title: android - the apk must be signed with the same certificates as the previous version
body: <p>I am trying to upload my Android app to the Google Play market and I get the error:</p>
  
  <pre><code>the apk must be signed with the same certificates as the previous version
  </code></pre>
  
  <p>The funny thing is I am using the original keystone with the original passwords, so I am confused as to what could be causing this problem.</p>
  
  <p>1)  I did upgrade my Mac OS X to Lion which a 64 bit OS from I think the earlier 32 bit OS.  Could that be the problem?</p>
  
  <p>2)  I did update the Android tools: Eclipse, SDK and Java before making this new app version.  Could that be the problem?</p>
  
  <p>3)  I also tried running</p>
  
  <pre><code>jarsigner -verify -verbose -certs
  </code></pre>
  
  <p>on the old version of the app that is on Google Play and the new app and the certificate valid times are the same.</p>
  
  <p>4)  I created the new APK both manually and by using Export Android Application in Eclipse.</p>
  
  <p>5)  Manually I created the APK by within Eclipse using `</p>
  
  <pre><code>Android Tools -&gt; Export Unsigned Application and then using
  jarsigner -verbose -keystore mykeystore.keystore app.apk companyName
  /Developer/android-sdk-mac_86/tools/zipalign -v 4 app.apk app_aligned.apk
  </code></pre>
  
  <p>So I don't think the problem is that I am using the wrong keystore.  I've read that this problem could also be caused by</p>
  
  <p>A)  Trying to upload a debug apk instead of a release apk.</p>
  
  <p>B)  Having the wrong package name in the manifest.</p>
  
  <p>C)  Not incrementing the versionCode and versionName.</p>
  
  <p>Are there other things that could cause this problem besides using the wrong keystone?</p>