How can I find out which included code makes my universal binary iOS so big?

I have a great iOS app for iPhone and iPad. I optimized the images and reduced all related data to a minimum that made a reasonable difference, but now my application is 50% "Application Binary" - the only file containing all my code.

How can I find out what makes it so big and is trying to start thinning out possibly unnecessary files or dependencies?

+4
source share
1 answer

Open the project file in Xcode. At the bottom of the Summary tab, within linked Linked structures and libraries, you can see which libraries you are linking to. The frames are in order, you dynamically communicate with them, since their binary file is already on the phone. But you can also find here static libraries (with the extension .a) that are "copied" into your application bundle. This is called static linking. Therefore, they will make your bunch thicker. On the "Phase Assembly" tab, you can see which source files you are compiling and, thus, linking in your binary format, they make another part of the compiled program code. The rest of the package is resources, images, etc., but I think you already checked that.

+3
source

Source: https://habr.com/ru/post/1400020/


All Articles