Release 3.4.0 broken with Carthage about frames-ios

[harry-brown-cko]

Hi @sebskuse,
Apologies for the Carthage issue. We are planning to release a patch for this next week. Please use version 3.3.0 until then.

[harry-brown-cko]

Yeah @sebskuse we agree. This is definitely something we're considering for future releases.

[harry-brown-cko]

@sebskuse this issue was fixed as part of the latest release, 3.4.1. Please feel free to re-open this if you have any further questions.

[sebskuse]

@harry-brown-cko thanks, let me know if you need any help testing anything pre-release or want to run anything by us.

I notice there is a PR up here #58, although this seems to be for a test project rather than giving this repo a Cartfile (& resolved) and making the project discoverable by Carthage.

[harry-brown-cko]

Hey @sebskuse, thanks for the heads up. I think we're almost there with the fix now in PR #58. We have tested ourselves and it should now be fine. If you want to double check, point your Cartfile at branch bug/fix-carthage.

[sebskuse]

Hi @harry-brown-cko - just given this a go and it looks like it compiles after replacing FramesIos with Frames in our codebase, thanks!

As an aside, as a feature request - it would be great to drop the Alamofire dependency in favour of just using URLSession. Nowadays URLSession is just as powerful, there's less chance of a conflict between other dependencies that may use a different locked version of AF, and it's one less dependency for apps to bundle.