Hello Romano,

in client libraries version 1.x, there are some exceptions that we still throw from NSError methods because they are due to programmer errors. E.g. unsubscribing a table twice. Apple itself resorts to exceptions in such situations, to make the developer aware of the problem quickly.

Anyway, as stated before, since client library 2.0 the APIs have been redesigned and error handling is now fully asynchronous. No more exceptions or even NSErrors.

Regarding difficulties with our pods, a dependency we rely upon is distributed exclusively as a static library. As far as we know, to distribute a framework linked to a static library requires distributing the static library too, so that would not make any improvement. If you have better information to share with us, regarding these issues, we will surely consider them and take any appropriate step to improve our product.

Best regards,

Gianluca