CODEWITHSUNDEEP
iosxcodeunity-game-engine
Oliver Jones
Oliver Jones

Reputation: 1450

Xcode Archive Is Too Large

I have a Unity3D project that I've already released for iOS via Xcode. Previously the archive size was about 30-40Mb which I'm happy with.

I've now changed a few things within the Unity project, and rebuilt it for Xcode. Now when I archive it, the size is around 110Mb, which is huge compared to the previous file size. I only changed the logo, and splash screen design.

Also, when I rebuild the older version, the size isn't 30-40Mb anymore, it's 110Mb too!

So I'm guessing this is something to do with the new Xcode for iOS8? Not 100% sure, hence why Im asking.

Thanks.

Upvotes: 6

Views: 7408

Answers (4)

Leo Nguyen
Leo Nguyen

Reputation: 614

Try to turn off BitCode. Open XCode => Build Settings => search Enable BitCode. Set it to No.

Upvotes: 2

Scott Driscoll
Scott Driscoll

Reputation: 2929

The 'Estimated App Store Size' reflects the installed app size, not the download size.

I'm basing this off the following test:

(Unity app build) Estimated App Store Size: 140.8 MB, size listed in store: 33.4 MB. The splash images alone inside the package add up to 30 megs uncompressed (all my jpegs were converted to pngs) so there's no way the installed size is 33.4 MB. After install, if I go to settings -> general -> usage -> Manage Storage I see the app is 141 MB installed.

I'm not sure how to estimate the download size, which is what matters if you have an app you want to be downloaded over cellular network and needs to be under 100 MB downloaded.

I added this as a comment to the question, but I wish I had read this as an answer, so here it is.

Upvotes: 0

Mobile Ben
Mobile Ben

Reputation: 7341

I believe part of what is happening here is the additional overhead for the arm64 slice (unless you were already including the arm64 slice previously). I would not expect that much of an increase in size for the arm64, but it would still be roughly X2 on the app binary (minus the resources).

As of Feb 1, Apple requires arm64 support as well as the app being built with the iOS 8 SDK. The default Xcode build setting enables arm64.

What you can do is Show Package Contents on the xarchive and work your way to the app executable binary. You can then compare the size difference on the app executable binary from before and now. You can also run lipo -info on it to see all the slices from before and now. Note I am assuming you have an older xarchive to compare with.

I would then probably diff the rest of the resources (use something like Araxis merge) to see the differences in the files. This will let you see what resource files changed or got added. If your diff is only the executable, then you have isolated were the size difference has come from.

Upvotes: 1

Javi Barrera
Javi Barrera

Reputation: 43

Have you read this? http://docs.unity3d.com/Manual/iphone-playerSizeOptimization.html

Also it can be fault of stripping level, try to use micro mscorlib.

In addition you can take a look at Decrease Your App’s Code Size from Mac App Programming Guide. https://developer.apple.com/library/mac/documentation/General/Conceptual/MOSXAppProgrammingGuide/Performance/Performance.html#//apple_ref/doc/uid/TP40010543-CH9-SW2

Upvotes: 1

Related Questions