How to import a dynamic framework to existing Project

That's not the crash log; that's the console log. Check the Devices window in Xcode - select your device and click the Device Logs button. Hopefully there'll be an actual crash log there with some better info.

Hi Junkpile ... I have updated my post with Crash Logs ... can u plz help now to resolve the issue.

From the reason "image not found", I guess it's not correctly linked.

One way to easily import your framework is to just literally drag and drop it into the "Embedded Binaries" section of your target (General tab).

It would then display a dialog, select both "Copy if needed" and "Create Group".

After that, the framework should appear in both "Embedded Binaries", "Linked Frameworks and Libraries" in the General tab, as well as "Link Binary With Libraries" and "Embed Frameworks" in your Build Phases tab.

Hope it helps.

Hi EinharchAltPlus,

Thanks for your reply ... but Embedded Binaries is supported in ios8 and above.

We want to support ios6 and ios7 also.

While uploading as Embedded Libraries on itunes connect we are getting many irrecoverable errors.

Please suggest something were we can use use it as dynamic framework

Hi Junkpile...

Can u please help me to resolve the above issue

Oh, sorry, I can't help on this one.

Possible leads:

- I know some people doing many workarounds, such as weak linking the library ... But unsure how well it would do on earlier than iOS7

(search for quellish / Weakness on GitHub for an example).

- A more technical and harder solution would to use dlopen for example (a good description in Apple's documentation at: "Dynamic Library Usage Guidelines"). And you can check Facebook's open sourced iOS SDK to see how they do it in practice (mostly in FBSDKDynamicFrameworkLoader.m)

Personal thoughts:

I'd avoid doing that because officially, only iOS8 onward are supported, you'll have many troubles making the app work, and your app can be rejected even if you succeed.

I'd also ask the question if there's really any need to support iOS6, if a large chunk of your userbase is on iOS6, then you have a problem: you are missing the 99% of App Store users (check App Store access statistics, it counts updates, as people have to access the store to update their devices).

One last point to consider: If the library is a dynamic one, chances are it was built against iOS8 onward and using methods nonexisting in iOS6/7, so even weak linking and avoiding crashes, anything related to the libraries won't work on iOS6/7 ... So consider if it's a good thing to deliver an update to these users that is, at best, buggy, and offers no extra functionality.

An alternative solution: Get older static libraries if it exist, weak link it as well, and in code check which version of iOS it is before including the headers.