title: Android APK built from android studio and console have different SHA fingerprints
body: <p>While building signed release APK I've come across the following: if I build signed apk from android studio (via <code>Build</code> -&gt; <code>Generate Signed APK...</code>) with <code>build.gradle</code> file like this (only relevant parts):</p>
  <pre><code>signingConfigs {
      release {
          storeFile file('/keystore/location/mykeystore.keystore')
          storePassword 'storepassword'
          keyAlias 'key'
          keyPassword 'keypassword'
      }
  }
  buildTypes {
      release {
          signingConfig signingConfigs.release
      }
  }
  </code></pre>
  <p>The resulting apk fingerprint is <code>YY:YY</code>.<br />
  However, if I build my APK from console as described <a href="https://developer.android.com/tools/publishing/app-signing.html" rel="noreferrer">here</a> with <code>build.gradle</code> like this:</p>
  <pre><code>buildTypes {
      release {
      }
  }
  </code></pre>
  <p>And sign it with the same keystore file, the resulting apk fingerprint is <code>XX:XX</code>.</p>
  <p>Also, both SHA fingerprints are different from my debug certificate SHA fingerprint.
  What's the cause of such behaviour?</p>
  <p>I'm using buildToolsVersion 23.0.0<br />
  android studio gradle version 1.3.0<br />
  android sdk tools version 24.3.4<br />
  android studio version 1.3.1</p>