---
slug: "android-keystore-not-visible-sha256-fingerprint"
title: "When the SHA256 of the Keystore is Not Displayed with Keytool During Android App Development"
description: "In Android development, there was an issue where the SHA256 fingerprint was not displayed when trying to generate a keystore and display the fingerprint using keytool. This issue can be resolved by specifying the correct options with keytool. If this problem occurs, it seems that the SHA256 fingerprint is being displayed in the place of the SHA1 fingerprint."
url: "https://www.ytyng.com/en/blog/android-keystore-not-visible-sha256-fingerprint"
publish_date: "2021-12-26T03:09:45Z"
created: "2021-12-26T03:09:45Z"
updated: "2026-02-27T05:11:46.945Z"
categories: ["Android"]
keywords: ""
featured_image_url: "https://media.ytyng.com/resize/20230812/4af203139dd844fa8b798b26d71e5173.png.webp?width=768"
has_video: false
has_music: false
video_urls: []
music_urls: []
lang: "en"
---

# When the SHA256 of the Keystore is Not Displayed with Keytool During Android App Development

<p>When developing for Android and trying to create a keystore and display the fingerprint using keytool</p>
<pre>% keytool -list -v -keystore android/certs/app.jks<br />Enter keystore password:<br />Keystore type: PKCS12<br />Keystore provider: SUN<br /><br />Your keystore contains 1 entry<br /><br />Alias name: key0<br />Creation date: Dec 26, 2021<br />Entry type: PrivateKeyEntry<br />Certificate chain length: 1<br />Certificate[1]:<br />Owner: CN=....<br />Issuer: CN=....<br />Serial number: 37...<br />Valid from: Sun Dec 26 11:29:11 JST 2021 until: Thu Dec 20 11:29:11 JST 2046<br />Certificate fingerprints:<br /> MD5: AA:5C:31:23:...<br /> SHA1: B1:41:37:24:...<br /> SHA256: <strong>SHA256withRSA</strong><br />Signature algorithm name: 2048-bit RSA key<br />Subject public key algorithm: 3<br />Version: {10}<br /><br />Extensions:</pre>
<p>If the fingerprint that should be displayed under SHA256 is not shown, and instead "SHA256withRSA..." continues without a newline, it is because the language is set to Japanese.</p>
<p>According to a <a href="https://stackoverflow.com/questions/67447237/keytool-sha256withrsa-written-instead-of-an-actual-sha256-on-my-production-key" target="_blank">StackOverflow answer</a>, if the language is set to French or German, setting the shell variable <code>LANG=C</code> should fix it. However, that alone did not work in my environment.</p>
<p>Referring to another <a href="https://stackoverflow.com/questions/17646757/how-to-set-default-language-for-java-keytool" target="_blank">StackOverflow answer</a>, I added the option <code>-J-Duser.language=en</code> to keytool, and it worked.</p>
<pre>% keytool <strong>-J-Duser.language=en</strong> -list -v -keystore android/certs/app.jks<br />Enter keystore password:<br />Keystore type: PKCS12<br />Keystore provider: SUN<br /><br />Your keystore contains 1 entry<br /><br />Alias name: key0<br />Creation date: Dec 26, 2021<br />Entry type: PrivateKeyEntry<br />Certificate chain length: 1<br />Certificate[1]:<br />Owner: CN=...<br />Issuer: CN=...<br />Serial number: 37....<br />Valid from: Sun Dec 26 11:29:11 JST 2021 until: Thu Dec 20 11:29:11 JST 2046<br />Certificate fingerprints:<br /> SHA1: AA:5C:31:...<br /> SHA256: <strong>B1:41:37:...</strong><br />Signature algorithm name: SHA256withRSA</pre>
<p></p>
<p>After writing this, I realized that when the language is set to Japanese, the SHA256 fingerprint appears as a SHA1 fingerprint.</p>
<p></p>
<p></p>
<p></p>
<p></p>