iOS build size increase because of PVRTC texture format not recognised by Unity Could

Thanks for the post, as said we currently work on the problem, we will keep you updated on this issue in this thread!

 

tl;dr
PVRTC/ETC2 warnings can be ignored and do not have anything todo with your final build size.

Long Story:
E.g. Editor is set to iOS platform, textures are set to PVRTC for iOS. So Unity encodes textures as PVRTC while in the Editor, the catch is the Editor is currently running on a Mac which natively does not support PVRTC (only iOS and some Androids do), so for the Editor to display those textures, it has to decompress them on the CPU, thus that warning. This happens in all cases: Cloud, local builds, etc so you will see those warnings in your local Editor.log as well.

So the size difference is certainly not related to the warnings. What's the size on Android? Did you check the bitcode option as mentioned here?

You can also use the otool reports to find out if your assets are not compressed or if your binary has the size increased. Read more about it here.

 

Hey All,

Just jumping in to add a bit more detail about Local Build vs Unity Cloud Build (UCB) size for the iOS platform.

First some history and details:
Apple released tvOS and watchOS just recently and with it a new requirement for app submission: bitcode compile.
What is bitcode? Simple:

So that basically means that it will not compile the app completely into a final, tiny binary, but into a state that contains a lot more information. This additional information when uploaded allows Apple to generate multiple final, tiny binaries to target very specific devices. For example: There is no reason to include the larger art files if the device downloading the app only uses the smaller formatted files.

Now bitcode compile is not required for iOS currently, but in the future it might be required. Also as of Xcode 7, bitcode is enabled on all platforms by default. There is also one catch on this as well, bitcode is only generated in Archive builds. These builds are the final builds of your application that will be sent to the App store, and also this is what UCB uses to build your applications too. This way once you are done testing a build from UCB, you can turn around and submit it to the App store with no additional work on your part. So when you are doing builds locally, you are most likely doing just a quick Run build as seen in the below image. This build will not generate bitcode, and will be close to the final download size of your application from the App store. If you do an Archive build, you will end up with bitcode and all that will match the file you downloaded from UCB. Now if you really want UCB to not generate bitcode, David linked to a post build processor that will disable bitcode: http://forum.unity3d.com/threads/unity-5-3-x-build-size-increase-faq.383533/

 

What is the size when you do an Archive build locally and a Run build locally? Also what are you targeting when you are building locally? (Example: In my previously attached image, I have "Generic iOS Device" targeted.)