twilio / conversations-ios

SPM releases
https://www.twilio.com/docs/conversations/ios/changelog
10 stars 5 forks source link

Connection takes time iOS Swift #13

Closed aiyub007 closed 1 year ago

aiyub007 commented 2 years ago

Hi When I connect to client using below code ::

TwilioConversationsClient.conversationsClient(withToken: token,
         properties: nil,
         delegate: self) { (result, client) in
           self.client = client      
            }
 }

It takes time when there are more then 100 conversations

When I checked code, I got to know the connection obj client has conversation obj

Please give the resolutions . There must be pagination for the conversations. and connection obj stand alone connects rather then fetching conversations with it.

Thanks in advance.

Pavel-Cherentsov commented 2 years ago

Hello! Yes, Conversations Client on its init performs fetching and synchronising of all conversations the current user participates. So the more conversations - the longer init time. How long is it in your case?

jkottapa commented 2 years ago

@Pavel-Cherentsov I am @aiyub007 colleague, it takes anywhere between 8-10s and its pretty consistent in terms of the time it takes.

We expect there to be over 500+ conversations a single user could be subscribed to at any given time (mostly 1-1 DMs). Please advice.

Pavel-Cherentsov commented 2 years ago

Hi @jayanth1991, Well, such initialisation time looks as expected. Yes, with 500+ conversations it will be even some longer... In future we are going to speed up init on hundreds/thousands of conversations, can't provide no promises yet.

jkottapa commented 2 years ago

Hi @Pavel-Cherentsov its not a future problem, its actually happening right now for us and unless there is a workaround for this issue, its practically unusable under normal user behavior

Gray-Wind commented 2 years ago

Hello, we've made some optimizations and the client should behave better in cases of high loads. Could you check it now?

Gray-Wind commented 1 year ago

I'm closing the ticket since there is no more comment on this topic. Feel free to create a new issue.