-
-
Notifications
You must be signed in to change notification settings - Fork 170
Description
My app has a routine which checks the validity of an in-app subscription (via my own server). But I have found a hacked apk on a download site which somehow avoids this check, thereby giving free access to the in-app subscription. Nothing is ever received at my verification server, so they must somehow be faking this check.
But somehow this apk is not caught by the "signature" check made by PiracyChecker. How can this be... surely a hacked apk must have a different (and invalid) signature?
The "licence" check made by PiracyChecker does catch the hacked apk but I'm finding that there are too many false positives (apparently genuine users, maybe with slightly unusual setups) that are caught too.
If I can understand how the in-app purchase check is being avoided then maybe I can just tighten up the security within my code to thwart that.