Tobias Hagemann

Thank you, @daniel-moh, I'm very happy to hear the good news! 🎉 I can only speak for our own project but we've made use of these 3 PRs: - https://github.com/airsidemobile/JOSESwift/pull/268...

Not sure if I should open a new issue, but I have the following problem: I'm still getting the error, because CocoaPods sets the iOS deployment target of the MBProgressHUD...

It's a compile-time issue. I'm not aware of a way to silence the compiler in this case, because it's not a warning, it's an actual error. I've solved it for...

App Extensions seem to be something rarely implemented. In my opinion you shouldn't reduce code quality, just because of edge cases. Your suggestion would work and probably won't break anytime...

Just wanted to inform that using subspecs could be an elegant solution: https://github.com/CocoaPods/CocoaPods/issues/5373 Haven't tried it out myself, but I think this should be the way to go to deal...

Are you positive? I've revisited this issue and updated MBProgressHUD to 1.0.0 in my project. I was even able to remove my `post_install` hook workaround (which was needed for versions...

Thanks! Yes, you're right. OpenSSL is a static library and causes the issue, when using `use_frameworks!`. Haven't really thought of it, because I'm personally not a big fan of dynamic...

Afaik, it shouldn't be an issue to port/rewrite this library to/in Swift. But there hasn't been a need for this because Cryptomator for iOS is written in Objective-C. If you...

Better late than never but there has been a Swift alternative for quite some time: https://github.com/cryptomator/cryptolib-swift

This needs some refactoring but I'd like to remove versioning completely and just keep the docs up-to-date (which is hard enough already). If there is a need to look up...