title: Creating dummy Fabric Api keys for an open source project
body: <p>I am working on an open-source project (Kotlin, Toothpick, Clean Architecture - nowadays hype themes, but that's not the question :). I am using Fabric's Crashlytics, so I hid the API and secret keys into <code>fabric.properties</code>, according to the <a href="https://docs.fabric.io/android/fabric/settings/working-in-teams.html#android-projects" rel="nofollow noreferrer">the official docs</a> (and <a href="https://stackoverflow.com/a/47880170/3675659">here are some details</a>)</p>
  
  <p>The question is what is the best way to provide some dummy keys to collaborators without needing to solve merge conflicts in this properties file? If I publish the project without this file, it will crash on build because Fabric won't find needed keys.</p>
  
  <p>The options I see:</p>
  
  <ol>
  <li>Attach a <code>fabric.properties</code> with pre-defined API and Secret keys that are not from the actual app dashboard, so if somebody (intentionally or not) brakes analytics or something, their data will be in a separate dashboard.</li>
  <li>Do nothing, so if somebody interested they have to do it manually.</li>
  <li>Provide the real keys to the repo (I don't think that it is a good idea, but if you have other experience, share it please)</li>
  <li><p>Maybe, Fabric has some dummy keys just not to fail the build without them (I haven't found them)?</p></li>
  <li><p>Something else?</p></li>
  </ol>