Hi,
I am creating a dynamic framework in swift with some code in objective-c. The framework consists of xib files as well as images. After creating the framework, I add it to another project by embedding the binary (because if I only link the library, the application crashes saying that framework not found). Everything runs fine on device.
The error occurs when I archive the build and submit to app store.
After searching a lot on the internet, I found that by creating an universal library I can submit it to app store. I used a script to create the universal framework, checked with lipo if all architectures are supported or not. But universal framework did not solve my problem.
Also, when I remove the framework from embedded binaries and add it to link with libraries section, the archived build is successfully submitted to the app store. But the build crashes, due to reasons stated above. Thus, useless.
Finally, I ended up creating a static library. I made it just for testing by converting only a small portion of my swift code to objective-c. After creating the static library, I created a framework with it and included it in my project. Also, the static library has no xib or images, just plain simple code. The build was then successfully submitted to the app store.
Now I have a few important questions -
1. Is the problem due to the fact dynamic frameworks are intended to be used within the project for different targets, e.g. - watch, tv, extensions?
2. I don't want to convert my code from swift to objective-c. Is there a way for my dynamic framework to be accepted by app store?
3. If there is no such a way, and I painfully convert my code from swift to objective-c, is it futureproof considering the fact that swift is here and apple can pull the plug on objective-c?