Thanks for the PR. That seems sensible. What was the reason for lowering the version of TaskQueue?

Also, the dependencies in the Podspec should match the Cartfile, so I'll make some changes to the Podspec to match and push them to this branch.

I made the podspec and carthage consistent and switched all dependencies to == rather than ~> as CryptoSwift was somehow evaluating to 1.0.0 when it was set to ~> 0.15 which shouldn't be possible, but it was. I did put TaskQueue back to 1.1.1 - when I went through and put the values in for the dependencies I was looking at the releases on each repo, and TaskQueue hasn't been publishing releases even though they are tagging each one - so I put an old version in as a result. But it's now at listed as 1.1.1

Sorry, I didn't get round to pushing my changes. It looks like we ended up with roughly the same Podspec though. The only difference is that I don't think it's necessary to pin CryptoSwift and TaskQueue to precise versions. It's probably desirable to allow flexibility.

I've tested my version using both Carthage and CocoaPods and I get the correct versions installed. I noticed that ~>to means something different in Carthage vs Cocoapods, which could be why you were having problems, but I'm not sure how that would end up returning 1.0.0.

I've pushed my proposed changes. What do you think?

I appreciate that the versions don't match exactly between the Cartfile and Podspec but my reasoning is that:

• Starscream: updated to Swift 5 on a minor version. In Carthage ~> will update minor versions so we have to pin to an exact version. In CocoaPods however, we can use ~> to only update patch versions. It makes sense for us to allow flexibility where we can, whilst still holding the version back before that Swift 5 release.

• CryptoSwift: the Swift 5 release was 1.0.0, but the behaviour of ~> in Carthage is different in versions < 1.0.0 and won't update minor versions, so we can't express the same restrictions in Carthage and CocoaPods.

• Reachability: updated to Swift 5 on a patch version therefore we have to pin to an exact version in both files.

• TaskQueue: no recent changes.

@lukabratos and I reviewed this together in person and decided it's ready to merge.