title: Setting up Firebase for debug and release with a dev and release database
body: <p>I have two build types - <code>debug</code> and <code>release</code> - and two flavors, <code>dev</code> and <code>prod</code>.</p>
  
  <p>The distinction is straightforward: <code>debug</code> is a debuggable binary, <code>release</code> is optimized, has debug code removed, and Proguard.</p>
  
  <p><code>dev</code> is meant to connect to a development Firebase project, <code>prod</code> is for the actual production database.</p>
  
  <p>There are cases when I would like to use <code>debug</code> in the prod database, so I have all four possible combinations. The problem is that the project settings in Firebase require the SHA1 fingerprint of the signing key of the binary, and creating a debuggable application will always use the debug key.</p>
  
  <p>I can't have the same key on two Firebase projects, so having the debug signing key on the dev Firebase project means I can't also have it on the prod one, so I cannot use the "prodDebug" setup (i.e. prod database with a debuggable binary).</p>
  
  <p>What's the proper way to resolve this?</p>