I read all the different ways posted in this thread, and the encryption check seemed the best and safest way to go. I've implemented it and I'm in the same situation as above. However I compile my app, I get a crypt_cmd->cryptid equal 0, for all (non-simulator) targets and all configurations.
The assumption though is that binary encryption won't actually occur until Apple signs the binary.
I used the otool -l command to check binaries I previously submitted to Apple and the cryptid is 0. I use it on all apps I downloaded from the App Store, including my apps, and the cryptid is 1.
So I'm not worried about this, binary encryption will occur when Apple signs it and puts it in the store.
But, my concern is this: When the reviewer puts it on their device to test it, is the binary already signed by Apple and therefore encrypted? Cause if it isn't, then the app will think the reviewer is running a pirated copy right?
|
