Hi,
First of all, I'd like to thank everyone from the iphonedevsdk community for sharing all their knowledge. I have learned a lot from these forums, and have nearly always found an answer to questions I had regarding iOS development.
I'm in the same boat as a lot of people here, have released my first app a few weeks ago, and, despite it not being a general public app, it has already been cracked and put on appulous.
It has been cracked by an automated cracking program (there's a text file in the .ipa package that actually mentions this: "[...] Cracked by [...] using Clutch 1.1 RC2.").
So I'm looking into implementing some anti piracy checks to try and turn the cracked app into a demo version for the future updates.
I have implemented a few techniques in this thread, but have a few questions:
Quote:
Originally Posted by Damian
And here it is
Code:
if(fabs([infoModifiedDate timeIntervalSinceReferenceDate] - [pkgInfoModifiedDate timeIntervalSinceReferenceDate]) > 600) {
//Pirated
}
if(fabs([infoModifiedDate2 timeIntervalSinceReferenceDate] - [pkgInfoModifiedDate timeIntervalSinceReferenceDate]) > 600) {
//Pirated
}
|
This doesn't seem to work, on simulator or on device (SDK 4.3).
The second check:
Code:
fabs([infoModifiedDate2 timeIntervalSinceReferenceDate] - [pkgInfoModifiedDate timeIntervalSinceReferenceDate]) > 600
always seems to return true ?
Anyone else getting this ?
Also, concerning the encryption check: does this entail that we need to declare that our app uses some form of encryption when we submit it to Apple (thus leading to a lot of red tape procedures etc) ?
I also just wanted to double check about the info.plist filesize. This check works fine when I run the app on my devices, although I have noticed that the file size changes if it's being run in the simulator.
Is the file size (on the device) going to be the same as the debug one when using the release scheme ?
Many thanks,
Regards