-
Notifications
You must be signed in to change notification settings - Fork 8
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
XCFramework shouldn't be distributed with Swift standard libraries #13
Comments
@username0x0a fixed. We are changing the deployment target as well as additional fixes and then releasing it. We are aiming for a Friday (May/27) release |
Thanks for info 👍 I'll be floating around to give a feedback, shall you need some before the release. 👌 |
Hello @mooseriskified , |
@adellibovi We moved it to Tuesday ( tomorrow ) as we identified a simple bug in the pre-release. Ill ping you once we release it |
Will it fix also the issue mentioned about with Bitcode generation @mooseriskified ? #15 |
@adellibovi yes that was fixed |
@username0x0a we fixed the issue, let me know how it looks on your end |
Analysing the
1.3.0
update, I've noticed a great increase in thexcframework
bundle size. Looking closely, the framework now carries Swift standard libraries. These should be only bundled to the target app if needed (and deploying to iOS 12.3 and earlier OS versions) or not at all as for later deployment targets, Swift 5 ABI compatibility handles it.Please rebuild the
xcframework
without the Swift standard libraries bundled. 👍The text was updated successfully, but these errors were encountered: