Massive IPA size Xcode 7 Archive

Archives now contain bitcode by default, which you send to the store but which will never actually wind up on users' devices (since the store strips it out of the IPA it produces for users). If you do an ad-hoc export of your app from the archive to get a user-style IPA, however, you should see the true size without bitcode, as we'll strip bitcode out in every export scenario except submitting to the app store.

So this shouldn't actually be a problem; but please do le us know if you're seeing something other than what I've described.

Thanks Rick!

Looks like TestFlight finally processed it and we've actually shaved some bytes off 🙂

Hi, please find time to answer.

In Xcode 7 I developed simple universal iOS app, deployment target is iOS 8.
Then I archived my project with 'Release' build configuration.
In 'Organizer' I exported an .ipa file from it's archive.
I noted that .ipa file is about 3.3 Mb and that was as I expected - because my app is simple (there is no huge code base, no huge graphic assets).
But when I distributed my app with OTA (Crashlytics) and installed it on iPad - I noticed that iOS 'Settings' app shows me about 51 Mb of storage space for my app.

I am using iPad with iOS 8.4.
So I am little bit confused - why is that? Why difference is so big ?

Hi Rballard,

My iOS app does not uses Swift and is not targeted for WatchOs and no bit code is disabled.

The ipa size that is created out of XCode 7 is 30mb. But when its uploaded to testflight, the size is shown 58 mb in testflight app.

Its giving a completely wrong size information to stakeholders who will be accessing the build.
Can you please explain the following: a) Why this behavior is happening in testflight. ?

b) Will the same size of 58 be shown for users in Appstore or the 30mb ipa size which was uploaded to Tesflight. ?

c) How can i get a the correct information from testflight and appstore on app size, to convey the same to stake holders. ?