Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/redth/android.signature.tool
Simple GUI tool for Mac and Windows to help find the SHA1 and MD5 hashes of your Android keystore's and apk's
https://github.com/redth/android.signature.tool
Last synced: 10 days ago
JSON representation
Simple GUI tool for Mac and Windows to help find the SHA1 and MD5 hashes of your Android keystore's and apk's
- Host: GitHub
- URL: https://github.com/redth/android.signature.tool
- Owner: Redth
- Created: 2014-06-18T17:03:34.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2014-06-20T19:54:30.000Z (over 10 years ago)
- Last Synced: 2024-10-17T07:34:45.686Z (21 days ago)
- Language: C#
- Size: 593 KB
- Stars: 38
- Watchers: 4
- Forks: 13
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Android Signature Tool
There are a number of services (Google Maps, Amazon to name a couple) which require that you get a MD5 or SHA1 hash/signature from the keystore file that's used to sign your app so that the service can generate a custom api key for you.
This is generally a pain, and finding these values is quite tedious. There is a nice guide up on the Xamarin documentation about this subject if you are interested: [Finding your Keystore's MD5 or SHA1 Signature](http://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/MD5_SHA1/)
However, this tool is meant to make it a bit quicker to find these values, especially if you are using Xamarin.Android.
### Default debug.keystore for Xamarin.Android
If you are using Xamarin.Android, by default your app is signed with a debug.keystore file (you probably didn't even know this, or need to, which is a good thing!). This tool can track down that auto generated .keystore file (which is the same for all your apps, by the way) and grab the hash/signature for you by just clicking a single button. This way, you don't need to know where keystore tool is, or where the debug.keystore was generated.
### Signed apps
If you are releasing to the Play Store, you've no doubt signed your app with your own .keystore file which you created. You can still use this tool to find your hash/signature in that case, you just need to know where your .keystore file is located and what the alias/keypass/storepass are for the file.
