title: How to sign an APK with more than one certificate?
body: <p><b>How do I sign an APK with more than one certificate, so that I can do this when I publish to the Android Market:</b></p>
  
  <p>Version 1.0 => Signed with Certificate A<br>
  Version 2.0 => Signed with Certificate A &amp; B<br>
  Version 3.0 => Signed with Certificate B  </p>
  
  <p>The Android Market does give me some hope but I am not sure what to make of it, when I upload with a different sign certificate it gives me this message:</p>
  
  <blockquote>
    <p>"The apk must be signed with at least one certificate in common with the previous version."</p>
  </blockquote>
  
  <p><b>Motive:</b><br />
  I have published an app on the market using the Android Signing Tool as part of MotoDev Studio for android. The problem is that it handles the keys itself and there is no way (documented) to get them. I want to change it to use a keystore and certificate that I have more control of and can use even if I don't use MotoDev Studio anymore.  Also it seems that MotoDev Studio will lock you out of new features such as shared libraries.</p>
  
  <p><b>UPDATE 5/3/2011:</b><br /> They have been actually really quick and prompt at updating MotoDev Studio but it seems like I believe that Google should still provide a work around for those that want to change the certificates of their applications. Updating application to all use the same certificate, creating new ones over time, and possibly creating a new one so that you may hand of the support and distribution of your application to others.</p>