Search:

Hello again guys,

we finally nailed it. Find out more about support for SPM and Apple Silicon on our latest blog post: Introducing support for Swift Package Manager and Apple Silicon.

Let us...

Hello dehesa and eric280,

using your suggestions we were able to build a distribution of the latest version (4.3) of our client library as an XCFramework. Thank you very much for sharing them with...

Hello,

thank you for your valuable insights into the problem. I will surely take a look and let you know.

Thanks for your information. We will surely take a second look at supporting SPM.

And sorry for the late answer, unfortunately your post was flagged for moderation (probably due to links) and it...

Hello,

no, Java is surely not the culprit. In fact, our client library does not contain or incapsulate Java code, nor a Java Virtual Machine, by any means. It contains only pure Obj-C code...

Thank you very much. It's a team effort of course, I'll forward your words to the other people of the team.

Our client library uses only native components for networking: NSURLSession on HTTPS transport, and CFStream on WebSocket transport.

The mechanism we use is a simple dependency injection pattern:...

Hello again,

we investigated the matter, and I’m afraid we have bad news. As reported even at the very beginning of the official documentation, a Swift package can't contain binaries.

We could...

Hello,

we are investigating the problem. If it will be possible to wrap our client library in a Swift Package, we will surely do. Anyway, consider that we will wait for Xcode 11 to be GM before...