Include SDK without dependencies

[appboy]

Include SDK without dependencies

[Wenzhi]

Hey @keith,

We are planning on releasing a beta version SDK to support SDWebImage 4.0 around the end of this week or early next week. Is the timeline good for you?

Thanks,
Wenzhi

[keith]

Is the SDWebImage GIF subspec required for the UI portion of Appboy? This adds another library to our project 😞

[Wenzhi]

Hey @mlloyd,

Thanks for reporting the issue! However, your issue doesn't relate to the original issue here. Could you create a separate issue following our issue template? It will help collecting more necessary information and stop notifying other people in this thread with an unrelated issue.

Let's move the discussion to your issue thread! We will try to solve as fast as we can.

Thanks,
Wenzhi

[Wenzhi]

Hi Keith,

It makes total sense not to include SDWebImage if you don't use or plan on using Appboy's UI features. The reason we force it as a dependency is because the current SDK's built-in in-app message feature will crash on display without SDWebImage present. Forcing everyone to include SDWebImage allows clients who don't currently use in-app messages to try them out later without worrying about crashes on older apps.

It's on our roadmap to separate the SDK into two parts: base and UI and we are working on it as we speak. When finished, we will change the podspec to different subspecs. It will not be finished in the near future, but we will let you know right away when it's done.

If you have any suggestions about how we can make things easier for you, or any other questions, please let us know.

Thanks,
Wenzhi

[keith]

Thanks! We'll keep an eye out for the split update!

[jgrandelli]

👍

[hovox]

👍

[anna-sakhlyan]

👍

[keith]

Any update on the split here? Otherwise do you have any plans to upgrade SDWebImage to the newest major release?

[keith]

Sounds good, thanks!

[Wenzhi]

Hey @keith,

We released the 2.26.0-beta version with SDWebImage 4.0 support over the weekend. It would be great if you can try it out and let us know any issue or problem you see.

Thanks,
Wenzhi

[mlloyd]

Hey @Wenzhi

I have tried the Carthage 2.26.0-beta but the SDWebImage framework isn't working. Comparably with the version built direct from SDWebImage using Carthage.

I believe the issue is due to your zip including, the SDWebImage framework. Which is not the correct module header. It's incorrectly labelled, SDWebImage_umbrella.h Normally the include would be, #import <SDWebImage/SDWebImage.h>

For reference;
https://github.com/rs/SDWebImage/blob/4.0.0/WebImage/SDWebImage.h

Thanks, Martin

[Wenzhi]

Hey @keith,

We are currently working on creating a core suspec with no dependency to solve this specific issue. There is no timeline for the release yet but it should be in the near future. I'll inform you in this issue thread as soon as it comes out. Please stay tune :)

Thanks,
Wenzhi

[hovox]

We are not using any of the ui components. Having model and UI in the separate repos would be the best option for us.

[Wenzhi]

@keith/all,

We just released version 2.26.0 with two subspecs: Core and UI. The Core subspec has no dependencies. If you don't use Appboy UI components and want to include our library without dependencies, please change your Podfile to use Appboy-iOS-SDK/Core.

If you use the Core subspec - in the future you may want to message users using Appboy's UI, and shipping a version without our full library can introduce friction. For example, you may have to version-filter delivery of in-app messages and News Feed items.

Note: there are still resource files in the Core subspec. Eventually all UI items will be moved to the UI subspec.

For more information, please see (CHANGELOG.md)[https://github.com/Appboy/appboy-ios-sdk/blob/master/CHANGELOG.md]. Please let us know if you see any issue or have any questions.

Thanks,
Wenzhi

[mlloyd]

@Wenzhi
Is it possible to use the core version with Carthage?

[Wenzhi]

Hey @mlloyd,

Currently, our Core subspec does not have Carthage support because we support through a pre-built framework of our entire library. We are actively considering strategies for more robust Carthage support but don't have any plans for an immediate change here. We will keep you posted when we have more information.

I created a separate issue here to keep track of this Carthage support.

Thanks,
Wenzhi

[Wenzhi]

Hey All,

I'm going to close this issue as we now provide Core SDK without dependency on Cocoapods. If you see any issues or have any questions, please create an issue and let us know. :)

Thanks,
Wenzhi