Is my copy genuine?
Every official release is signed with the same certificate. If the fingerprint matches, the app came from us and has not been changed.
Signing certificate
SHA-256 fingerprint of the release signing certificate:
D8:00:B8:8F:4C:36:EB:F0:94:60:3B:48:40:29:B4:D5:04:33:A4:A4:09:48:24:CD:EC:A3:5C:07:3B:56:B8:09On the phone
Open the app, go to Settings → About, and compare Signing certificate SHA-256 with the value above. It must match exactly, on every version.
On a PC, before installing
With the Android SDK build tools installed:
apksigner verify --print-certs ExpenseTracker-v1.0.9.apkThe Signer #1 certificate SHA-256 digest line must read:
d800b88f4c36ebf094603b484029b4d50433a4a4094824cdeca35c073b56b809Delete the file and download the APK again from this site or the GitHub releases page.
Checksum of the download
Each release also has a .sha256 file next to the APK. It proves the file was not damaged or swapped while downloading. On Windows (PowerShell):
Get-FileHash .\ExpenseTracker-v1.0.9.apk -Algorithm SHA256On macOS or Linux:
shasum -a 256 ExpenseTracker-v1.0.9.apkThe result must equal the value inside the matching .sha256 file. Use the version number of the file you actually downloaded.
Why both?
The checksum tells you the file is the one that was published. The certificate tells you who published it, and it is also what Android checks: an update signed with a different certificate will not install over your existing app, which protects your data.