-
May 21st, 2016, 08:28 AM
#13
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
Similar Threads
-
By Anatoly Gurfinkel in forum Client SDKs
Replies: 9
Last Post: July 6th, 2015, 04:24 PM
-
By LS_Developer in forum Client SDKs
Replies: 3
Last Post: February 14th, 2013, 02:47 PM
-
By mibrahim.youxel in forum Client SDKs
Replies: 4
Last Post: December 3rd, 2012, 09:49 AM
-
By bor306 in forum Client SDKs
Replies: 7
Last Post: July 11th, 2012, 02:28 PM
-
By Alessandro in forum Client SDKs
Replies: 0
Last Post: March 28th, 2011, 03:06 PM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 10:02 AM.
Bookmarks