Re:Android App Reverse Engineering 101
by wolfi1 on Friday May 03, 2019 @12:29AM
(#19815559)
that begs one question: where to get the apk from?
[ Parent
| on HN ]
Next to the other suggestions there's evozi's apk downloader that generates apks based on pasted Google Play URLs[0] and the ability to download apks in the proxied Play Store replacements 'Yalp' and 'Aurora' which are available in F-Droid
You can either install it from your real hw device and, once connected via usb, do a $ adb pull test.apk or you can download it from these sites:
(I've tried them both for different RE purposes and they also have the latest updates for a lot of apps) APKCombo [1] & APKPure [2].
[1] : https://apkcombo.com/
[2] : https://apkpure.com
From your device using adb pull?
Re:Android App Reverse Engineering 101
by scrollaway on Friday May 03, 2019 @02:23AM
(#19816025)
Is there a more reliable way to get the APK programmatically, without having to use an android device as a middleman?
I know of gplaycli (https://github.com/matlink/gplaycli/) but its reliability leaves a lot to be desired afaik.
There is also the Yalp store (open source Google Play service front-end), as well as a bunch of third party websites that will happily give you an untrusted APK (they all claim to be secure and original, but somehow the sha2 hashes of identical versions are n=3 always different for me).
Could it be that it's a case of multiple APK? Perhaps different CPU architecture? In any case I would check the value of versionCode first (https://developer.android.com/guide/topics/manifest/manifest...).
Re:Android App Reverse Engineering 101
by sschueller on Friday May 03, 2019 @05:22AM
(#19816789)