Ios – Does Apple modify iOS application executables on apps submitted to the App Store


Is an app's executable file byte-for-byte identical when the app is purchased through the App Store and installed on a user's iPhone, compared to the original executable file submitted to Apple in the original app bundle? Or is it different (for example, with additional signatures or encryption)?

I am concerned only about the executable file, not the entire app bundle.

In particular, would code such as …

int main(int argc, char* argv[]) {
   FILE* file = fopen(argv[0], "rb");
   // Read entire contents of executable file; calculate a hash value
   // ...

… calculate the same hash as calculating the hash outside of the iPhone on the original, submitted executable?

For example, calculating a SHA256 hash as above then using "Build and Run" in XCode to run on an attached iPhone produces exactly the same result as calculating the SHA256 hash by running openssl sha256 MyAppExecutableFile from a terminal in OS X. This means the act of installing the app through XCode does not alter the executable file.

My question is whether or not this still holds when an app is submitted to the App Store, purchased, and installed.

Best Solution

The application executable is encrypted by Apple when released on the App Store, so self-running a checksum on your own binary is not a good idea —you cannot know the file size of the encrypted binary in advance—.

Mind you, the binary always remains encrypted in the file system, and only the iPhone root user can decrypt these binaries. If you download an app from the App Store with iTunes, you can open the IPA on your PC or Mac and see that the binaries are indeed encrypted by running otool:

otool -l <app binary> | grep cryptid
crypt id 1
(a value of cryptid 1 means the app is encripted)

otool -l <app binary> | grep cryptsize
(size of the encrypted segment)