1

I am developing a game and I would like to include some in-app purchases.

I decided to store the purchased items in a database and adding some checks to it. However, there is still one problem: Wouldn't it be possible to simply disassemble the app, exchange the response codes (eg. USER_CANCELED with OK) so, every time I open the dialogue and abort, my game thinks I bought the item?

I did try it on my app so far, however as I lack experience with baksmali, I didn't work for me. In theory, would be (easily) possible? And if yes, what exactly do you have to change in smali and what are countermeasures?

Thanks!

Force
  • 6,312
  • 7
  • 54
  • 85
  • 1
    [this](http://stackoverflow.com/questions/5536532/in-app-billing-security-and-design-questions) thread might interest you – Krishnabhadra Nov 03 '11 at 11:56

3 Answers3

2

Android has an In-app Billing security guidelines doc:

https://developer.android.com/google/play/billing/billing_best_practices.html

This question will invariably pop up all the time and the answer is that there's no "real solution" that will defeat all piracy. However, there are various techniques that will mitigate the problem and prevent piracy on a large scale.

It is up to the app developer to decide how far he/she is willing to go to limit piracy. Multiple versions through obfuscation and server-side verification and revocability are good techniques, more than that is probably overkill. The conventional wisdom is that it might not be important to worry about the small number of people who have the time and knowledge to hack one instance of the app.

VSB
  • 9,825
  • 16
  • 72
  • 145
Mihai Ionescu
  • 2,108
  • 1
  • 12
  • 15
0

If you decompile, change code and pack it again as apk, it needs to be signed with the same key you used before - or it won't be possible to make in app purchases through Play Store with it.

The items on the store can only be accessed by an app similarly signed as the one you uploaded through console.

However, it is possible to mimick the process without even reaching the store if someone completely changes the code. To prevent this, you should check for the legitimacy of the purchase through a back-end server. You may want to check this question and the answer on how to do that.

Community
  • 1
  • 1
Guven Salgun
  • 101
  • 5
0

Just an opinion: I don't have much knowledge about android apps, but about the security scope, You should make a decision about prevent cracking of your software or not or how much. The higher security will yield a more troubled application in time and cause your real customers feel bad or will steal their time (because of the decreasing performance). And you will spend your time to secure your application instead of making it a better and more useful. I advice you to read this nice comment too. "if people want your application cracked they will"

Community
  • 1
  • 1
Emre Guldogan
  • 590
  • 9
  • 19
  • I know, that it is *impossible* to have an "uncrackable" app - still I wonder, how easy it would be to modify the in app billing. Because, after watching that video that is mentioned in Krishnabhadra's thread, I am still convinced, that you could just modify the app to always return true. Is there maybe a ressource about hacking in game purchases on the web? Because I googled a little bit and didn't find any.... – Force Nov 03 '11 at 15:44