No Such Module 'Moltin' about ios-sdk

[craigtweedy]

Hi,

At the moment, unfortunately, we only support Swift projects. This is due to a few Swift specific language features we use from the V2 branch onwards, such as generic enums and typealias.

I'm looking into ways to support Objective-C but at the moment the use of these language features are holding us back. Replacing typealias with the underlying types should be easy enough, but replacing the generic enum needs some thought put into it. I could replace it with a boxed object, but this will affect how people interact with the data returned which is a breaking change (although maybe a necessary one).

[x697]

Hi Craig, I am using a Swift project. Should I just be installing the pod and importing it? Thanks for the response.

…

On Mon, Apr 23, 2018 at 8:38 AM, Craig Tweedy ***@***.***> wrote: Closed #21 <#21>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcXbT5shPqRuuUSaqj4MECZd48xRjWC_ks5trctNgaJpZM4Te-Eg> .

[x697]

Simply adding "pod 'Moltin'" to my Swift project installs the pod but when importing Moltin there is still no such module found. This issue is extremely frustrating and a solution would be appreciated.

…

On Mon, Apr 23, 2018 at 3:44 PM, Aditya Bose ***@***.***> wrote: Hi Craig, I am using a Swift project. Should I just be installing the pod and importing it? Thanks for the response. On Mon, Apr 23, 2018 at 8:38 AM, Craig Tweedy ***@***.***> wrote: > Closed #21 <#21>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#21 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AcXbT5shPqRuuUSaqj4MECZd48xRjWC_ks5trctNgaJpZM4Te-Eg> > . >

[craigtweedy]

Hi,

I'm sorry this is obviously not ideal for you. I'm looking at this as a priority and I am currently testing a fix for this. Will get back to you ASAP with a confirmation.

[craigtweedy]

Hi @x697 ,

Just a quick update. I've pushed up version 3.0.5 of the Moltin pod. This corrects the majority of the issue I believe you were having, however on testing that I'm getting some issues with code signing. This is something I'm currently still looking into, but I figured I'd update you on this anyway.

In the meantime, there is a way you can work with the latest Moltin SDK separately from CocoaPods:

• Download the 3.0.5 code directly from the master branch, or from this tag
• Drag moltin.xcodeproj into your project.
• Go to your targets Build Phases
• Click the plus icon under "Link Binary With Libraries"
• Add moltin.framework - I'm guessing you're integrating to iOS, so select moltin.framework from moltin iOS target.

I'll keep you updated as soon as I've fixed this code signing issue.

[x697]

Just tested the updated version with my project, and it works! I used cocoapods. Thanks for your prompt response to the issue, and good luck with the code signing problem.

…

On Mon, Apr 23, 2018 at 6:45 PM, Craig Tweedy ***@***.***> wrote: Hi @x697 <https://github.com/x697> , Just a quick update. I've pushed up version 3.0.5 of the Moltin pod. This corrects the majority of the issue I believe you were having, however on testing that I'm getting some issues with code signing. This is something I'm currently still looking into, but I figured I'd update you on this anyway. In the meantime, there is a way you can work with the latest Moltin SDK separately from CocoaPods: - Download the 3.0.5 code directly from the master branch, or from this tag <https://github.com/moltin/ios-sdk/releases/tag/3.0.5> - Drag moltin.xcodeproj into your project. - Go to your targets Build Phases - Click the plus icon under "Link Binary With Libraries" - Add moltin.framework - I'm guessing you're integrating to iOS, so select moltin.framework from moltin iOS target. I'll keep you updated as soon as I've fixed this code signing issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcXbT6RyjFdTSGjYmZbq79KZAYrX53NPks5trlmRgaJpZM4Te-Eg> .

[craigtweedy]

Oh! That is odd! In that case, it seems like the code signing issue is just on my side then!

I'm going to leave this issue open for a little while, and do some more testing on that side of the codebase, but in case it pops up for anyone else.

Thanks for your patience with this, I appreciate how frustrating these integration problems can be. I've already made some notes on areas we can improve to avoid these issues in the future.