title: Apksigner does not verify signature
body: <p>i was trying to verify the signature of the latest Gmail App (Version 8.11.25.224) with apksigner and it failed.</p>
  
  <p>I used:</p>
  
  <p><code>apksigner verifiy --verbose --print-certs &lt;apk.file&gt;</code></p>
  
  <p>The result was:</p>
  
  <pre><code>DOES NOT VERIFY
  ERROR: APK Signature Scheme v2 signer #1 Malformed additional attribute #1
  </code></pre>
  
  <p>I was searching for an explanation why this happend but I couldn't find any solution to this problem. I have experimented a little and if you add <code>--min-sdk-version 28</code> to the options of apksigner command then the results are:</p>
  
  <pre><code>Verified using v1 scheme (JAR signing): false
  Verified using v2 scheme (APK Signature Scheme v2): false
  Number of signers: 1
  Signer #1 certificate DN: CN=Android, OU=Android, O=Google Inc., L=Mountain View, ST=California, C=US
  Signer #1 certificate SHA-256 digest: f0fd...
  Signer #1 certificate SHA-1 digest: 3891...
  Signer #1 certificate MD5 digest: cde9...
  Signer #1 key algorithm: RSA
  Signer #1 key size (bits): 2048
  Signer #1 public key SHA-256 digest: 2b06...
  Signer #1 public key SHA-1 digest: b2da...
  Signer #1 public key MD5 digest: a90c...
  </code></pre>
  
  <p>And if you use the jarsigner tool the results are:</p>
  
  <pre><code>
  WARNING:
  This jar contains entries whoes certificate chain is invalid.
  Reason: PKIX path bulding failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  This jar contains signatures that does not include a timestamp. Without a timestamp, users may not be able to validate this jar after the signers certificate's expiration date (2036-01-08) or after any future revocation date.
  </code></pre>
  
  <p>Re-run with the <code>-verbose</code> and <code>-certs</code> options for more details. I uploaded my Gmail APK file.</p>