So it took us a while, but we finally moved our core project to Unity 4.
Everything works great except that today we noticed that the build size of the project increased about 14 MB (the estimated size of the app after archiving).
What I did is take the the backup of the project that’s still in 3.5, opened it in 4.5.0 (or 4.5.2, checked both versions) without any changes (code, assets, everything is the same).
I checked the editor log, and other than around 600KB size difference in shaders, everything else is the exact same size. So my guess is it has to be unity.
Was there anything that changed between those version that could cause it? Is there anything we could avoid doing or change that would solve the issue? Or is this just something we have to accept as cost of moving to higher version?
Sorry if this was answered elsewhere, but I googled far and wide and couldn’t find anything.
I have answered it recently, but it doesn’t show up in searches. Unity adds features, they increase the build size. Apparently there are some changes on the way with Unity 5, but they might be Pro-only, and might come later in the cycle.
I understand that, but it would be nice to have a list of things like that will increase in size so you can prepare for this.
For example if textures will take x% more memory from now on they should let us know. I assume Unity devs know what exactly is increasing the size of the build, they could share that knowledge with us.
We have a similar issue, but it’s from version 4.3.4 to 4.5. The same code increased by 8MB when we generate a “estimate on AppStore”, when built with 4.5.
It seems odd that there is such a jump, so I’m wondering if anything else may be the cause?
There was a similar thread awhile back: ipa bigger in Unity4.5? - Unity Engine - Unity Discussions , and it seems it’s a problem with ipa compression. It could be that something changed in Unity’s serialisation that makes data less compressible. You can try to get, extract and compare contents of actual ipa files (they’re renamed zip archives) and see if there’s actual increase in the original data, or if it’s just less compressible. If it’s less compressible, then you can try to see stats in the archives and see what files are less compressible. Though, it’s a bit problematic, since unity packs all the assets into one file.