That sounds good, as long as you don't go on the internet and talk shit about the user if it is detected.

Popping a message like this would be good: "Sorry, this section of the app is incompatible with IAPCracker. Please contact support if you have received this message in error."

The users will still post on your forum and claim they don't know what iapcracker is. and argue incessantly despite having crash reports that logged it in memory

Jailbreaking and installing those hacks is difficult enough that your losses from it are likely to be low. So the question comes down to what your motivations are. Money-wise, it doesn't make much sense to tack on any more anti-piracy measures than there are already. You'd effectively be working for pennies designing and implementing your schemes with the amount of revenue they'd likely generate vs your losses from goodwill in the inevitable anti-piracy screw ups.

Personally, I prefer the pragmatic approach to the idealist. It's far less stressful.

But there are better ways of attacking fraudulent IAPs. Perhaps more effort, but certainly fewer false positives. http://developer.apple.com/library/ios/#documentation/Networ...