app specific hash code generation issue.

**Issue by [nikhil-sh](https://github.com/nikhil-sh)**
_Monday Jul 10, 2017 at 08:26 GMT_
_Originally opened as https://github.com/googlesamples/android-credentials/issues/14_

----

I have used various methods mentioned to generated hash code. I have tried them all. Problem is each method generated **different hash.**

I have tried them on both the debug.keystore and release keystore.jks

here is stackoverflow [question](https://stackoverflow.com/questions/45005130/sms-retriever-api-generate-11-char-hash-code-for-app-specific-keystore-file) for the same

I have tried following method:
Here are those various methods:

1. linux command as describe here - [help doc](https://developers.google.com/identity/sms-retriever/verify#computing_your_apps_hash_string)
2. [sms_retriever_hash_v9](https://github.com/googlesamples/android-credentials/blob/master/sms-verification/bin/sms_retriever_hash_v9.sh) file present in the sample code
3. By including [AppSignatureHelper](https://github.com/googlesamples/android-credentials/blob/master/sms-verification/android/app/src/main/java/com/google/samples/smartlock/sms_verify/AppSignatureHelper.java) from sample app.

Start by comparing the documented Linux command, sms_retriever_hash_v9.sh, and AppSignatureHelper.java, using both the debug.keystore and release keystore.jks described in the issue. Reproduce the differing hashes and check the linked SMS Retriever documentation and Stack Overflow question; done means the discrepancy is explained and the correct app-specific hash generation is identified.

Written by the indexing model from the issue text.