Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have checked that my app product size is around 10MB but when I build it for archiving it shows me the Appstore size as 20MB i.e. it almost got doubled. But when I see archive in folder its size is still 10MB, I dont know why this happening may be its due to support of both architectures i.e. armv6 and armv7. If I submit the app with 20MB what my final size on the Appstore would come. If anyone have any idea then please let me know.
The iOS App store servers will encrypt the executable binary inside your app bundle for customer downloads, thus making the app much less compressible than your current archive. This is because the random looking bits that result from encryption are not anywhere near as compressible as armv6 or armv7 machine code.
So the way to get a more realistic App store download size is to remove the executable from your app bundle, zip the bundle, note the zip size, then add the uncompressed executable size.
If you have large static data inside your C code that you don’t want to obfuscate, then moving that static data into a data file in the bundle might help reduce App store size.