Hi Sathya MANOHARAN, did you ever solve this issue and if so, how? We are having the same problem.
Hi Christophe, Thanks for your quick reply. 'contactId' and 'jId' are declared as local variables just before the call to CreateUser (see below). There are log messages in each branch of the callb...
For information, I have tried the latest version of the SDK (1.85.0) and I still get this exception.
Hi Vladimir, correct, testing on the sandbox server.
Hi Vladimir, There is still an issue here with the conversation array. In order to prevent users from having to log in every time they open our app, I am bypassing the login process if there is a c...
Hi Vladimir, Thank you for the update to the sample code. At first glance, my code matched yours so I was still confused as to why it wasn't working. Then I discovered that the issue was caused by ...
Hi Vladimir, Thank you for your reply. On the first question: I've upgraded my iOS SDK to version 1.73 and I can see now that the conversationsManagerDidAckMessage is also fired when the receiver...
Hi Vladimir, Thank you for your reply and sample code. I am using Swift and the Conversation object has no property called 'isSynchronised'. What I see is that when I call the resyncBrowsingCache m...
I have upgraded to SDK version 1.73 and the behaviour is still the same i.e. I can see the message "Login still valid, reconnect" in the console and the kLoginManagerDidLoginSucceeded event is fire...