Quote:
Originally Posted by Shmoopi
That's very strange, if everything is right it should never check for it during a simulator build, which is encrypted anyway, and would find it during anything else. Try running it during a release build after cleaning all targets and see if that works. If it doesn't, take your executable from the build, whether it be debug or release, open up terminal, and type "Otool -l *Drag your executable file here". When you do that, a long line of encryption code from the file will pop up, navigate to command 9 and look for the encryption status, it will be either a 1 or a 0. 1 means that the file is encrypted, 0 means the file is not encrypted. If it shows a 1 then you know their is something with code, if not then report back here and I'll check it and possibly get rid of that method, although I've never had a problem with it. Thanks for the heads up!
|
Thanks for the quick response. Here is the Otool -l command 9 for the release build:
Load command 9
cmd LC_ENCRYPTION_INFO
cmdsize 20
cryptoff 4096
cryptsize 622592
cryptid 0
So the file is not encrypted. The debug build was basically the same. Are only distribution builds encrypted?
btw, when I run in the simulator the program runs all the way through the is_encrypted function and then returns NO at the bottom.
