Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anyway to cut down the size of ios dependencies frameworks? #26

Closed
developerjackemail opened this issue Oct 10, 2018 · 3 comments
Closed
Labels

Comments

@developerjackemail
Copy link

Hello, thanks for your great work first, I'm trying to follow them and learning, and I'm a new Swift Learner. Is there any way to cut down the size of ios dependencies frameworks? I test with your Vibration ANE example, and the IPA size goes to 42M, I use the old Admob ANE with Objective-c written test project, an empty project IPA only take less than 20M. Was adding all these huge 'dylib' necessary?

image

@developerjackemail
Copy link
Author

And with distribution IPA version, the size goes to 70, on Vibration example project.

image

image

@tuarua
Copy link
Owner

tuarua commented Oct 10, 2018

Don't confuse IPA size with the size of the final app in the App Store.

The size increase are the official Apple Swift libraries. If you build an iOS app with Swift in Xcode it produces an ipa with the same Swift files (which is most new apps now)

It's important to know that this doesn't mean a user who downloads the app from the app store downloads a file the same size as your ipa.
After you upload the ipa Apple compress/strip/thin the app

Apple say this

The size of libswiftCore.dylib in your IPA, and the size of your IPA in general, is somewhat meaningless these days. The new thinning features in the store will remove unnecessary content from your app when delivering to specific devices, and libswiftCore.dylib contains bitcode even if your app doesn't. This bitcode is removed before your app is downloaded to a customer device.

https://stackoverflow.com/questions/41907323/what-is-the-file-size-overhead-of-the-bundled-swift-libraries-compared-to-an-obj

@developerjackemail
Copy link
Author

Thanks for your reply, understand now, great project!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants