Hacker News Reader

Comment by adomanico | Hacker News Reader

Unfortunately this doesn't seem to be the case.

Binary sizes in iTunes connect (from our Xcode 8.3 build) all were 2x-3x larger depending on device.

I think the size iTune Connect reports includes bitcode, and isn't representative of the size of the app once it makes it to a user's device. The information in the original bug report you linked to clearly shows the size increase is limited to the bitcode portion of the binary.

Why would they do that, visually in the store?

I'm not sure what you're asking here. Why would who do what?

Why would they show the full size including bitcode when you go to download it, when it doesn't get sent to the device anyway.

The size I'm referring to is shown in iTunes Connect, which is the administrative side of the App Store that the developer uses to manage their app releases. As far as I'm aware the size shown in the App Store's user-facing UI does reflect the size that will be downloaded by the device. I think it's possible to see this size in iTunes Connect, but since I don't myself have any apps in the App Store I can't easily verify this.

You can see the per-device estimated App Store file sizes in iTunes Connect:

(navigate to your app) > Activity > All Builds > (select the version) > (select the build) > App Store File Sizes

You need to look at the download size on the end user device, not the binary size in iTunesConnect.

That's troubling. :( Same for both swift and objC?

Reply on news.ycombinator.com