CocoaPods 1.5.0 comes with native support for building pods as static libraries. Since then, we were able to additionally reduce our app's size by integrating our dependencies using a static library instead of using frameworks.
Unfortunately you are shipping your SDK as a framework only, so we cannot integrate it using CocoaPods and static libraries.
Of course, it makes sense to bundle SDK code with resources as a framework.
Alternatively, it would be possible to build and distribute the SDK as static library using vendored_libraries, resources and resource_bundles in your podspec to copy the resources into the target bundle.
Is there a chance you could alternatively provide your SDK as a static library?
CocoaPods 1.5.0 comes with native support for building pods as static libraries. Since then, we were able to additionally reduce our app's size by integrating our dependencies using a static library instead of using frameworks. Unfortunately you are shipping your SDK as a framework only, so we cannot integrate it using CocoaPods and static libraries.
Of course, it makes sense to bundle SDK code with resources as a framework. Alternatively, it would be possible to build and distribute the SDK as static library using vendored_libraries, resources and resource_bundles in your podspec to copy the resources into the target bundle.
Is there a chance you could alternatively provide your SDK as a static library?