title: Can the certificate for signing an APK be shared?
body: <p>Our project has multiple android developers that all have access to the Google Play Console, in order to be able to publish APK updates from their respective computers.</p>
  
  <p>As mentioned in the docs and this post here :
  <a href="https://stackoverflow.com/questions/4843212/the-apk-must-be-signed-with-the-same-certificates-as-the-previous-version">The apk must be signed with the same certificates as the previous version</a></p>
  
  <blockquote>
    <p><strong>Question:</strong> </p>
    
    <p>Is there a way where first developer can share his certificate with second developer, such that second developer is able to publish APK updates to Google Play console?</p>
  </blockquote>
  
  <p>So far I didn't see any mention of this in the docs or discussion</p>
  
  <p>The initial release of the app was published by the first developer.  Now, the second developer would like to publish some updates as well.  However this seems to be blocked, such that only APKs signed from first developer's computer will be permitted for Update upload.</p>
  
  <hr>
  
  <blockquote>
    <p><strong>Update</strong></p>
    
    <p><em>For a more established team, I can see the cloud solution from the accepted answer working - but in our case, sharing the certificate file proved to be the most practical solution.  It was clean, fast, and solved the requirement without otherwise adding any additional layers to the stack.</em> </p>
  </blockquote>