Getting tr: write error after getting 11 digit hash string

[yash365]

I followed all the using keytool mentioned here : https://developers.google.com/identity/sms-retriever/verify#computing_your_apps_hash_string. in windows.

I got the 11 digit has string but it is not working and getting this output after following command: keytool -exportcert -alias PlayDeploymentCert -keystore MyProductionKeys.keystore | xxd -p | tr -d "[:space:]" | echo -n com.example.myapp cat | sha256sum | tr -d "[:space:]-" | xxd -r -p | base64 | cut -c1-11

Getting the following warning message: Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format tr: write error

Don't know why "tr: write error" is coming ?

[grahamsmith]

Have you tried using the in built get app signature method that should give you the value?

[yash365]

Hello @grahamsmith yes i tried that only at first the inbuilt method i.e. : final smscode = await SmsAutoFill().getAppSignature;

Use this sms format which mentioned: <#> ExampleApp: Your code is 123456 FA+9qCX9VSu

• In debug mode i got the AppSignature and is working fine in debug mode.
• But when I released the app in play store the same AppSignature didn't work.
• I followed all the steps mentioned here for production, mentioned here: https://developers.google.com/identity/sms-retriever/verify#computing_your_apps_hash_string in windows. But getting the issue that I have mentioned above.

[grahamsmith]

Ah I don't run Windows.

The signature method should work for a release build without submitting to the Play Store. You just need to run the build locally.

[yash365]

I tried that but didn't work.