Closed kuchmiyalex closed 1 year ago
@Gray-Wind could you please take a look?
Hi @kuchmiyalex!
If I understand it correctly the Conversations Client were not able to shutdown gracefully in 5 seconds, which led to crash instantiated from the operating system. We will look into the issue, but I need a bit more information. Would you be so kind to open a support ticket and provide some details for your use case such as:
debug
or trace
level.Please add a link back to the issue when you open the support ticket.
Hey @kuchmiyalex, any update on the above? Thanks!
@RicardoNunoAlmeida @Gray-Wind thanks, we have rolled back to v2.8.2 due to an unstable chat connection while the app is staying in the background and then returning to the foreground.
As for this crash, I can't reproduce and provide debug/trace logs. The user had about 400 conversations and every conversation had about 5-10 participants.
Hello @kuchmiyalex,
Can you elaborate on unstable chat connection in background? iOS application in general cannot have any background activity. The SDK must restore the connection once it returns back to foreground.
The provided crash trace indicates that the application itself actually was terminating, this is not a case about restoring from the background. We tried investigate into this issue without any success yet.
Do I understand it correctly, that in fact you are trying to solve the unstable re-connection after your application comes foreground? What is the indication of a bad behaviour of the SDK in this scenario? I am eager to help, but juggling with a lot of unknowns now.
Thanks @Gray-Wind I think the unstable state is not related to this issue for the crash, we're considering submitting a support ticket with a trace log for you to check.
In general, it looks like the conversation client state is connected, but there are no events coming through, this happens only for one of our testers and is not always reproducible for him.
You might still want to have a look at the trace log, after moving to the foreground at 2023-05-05 14:24:32 there are no callbacks firing until the end of the file, and there are no updates from the conversation client related to new conversations/participants. This user has a lot of activity as could be seen in the log above. After downgrading SDK this is no longer an issue for us.
Thank you for getting back to me with the additional information.
The SDK downloads all available conversations on synchronization and caches them. Subsequent calls are not going to the backend. The local cache updates whenever new conversation appears.
The same happens with the participant list in the each of conversations.
Are there any other indications of connection problems after restoring your application from the background? Are new convesations and/or participants being added after 2023-05-05 14:24:32
during visible 37 seconds of logs?
We will continue with checks on the proper reconnection of the SDK in the meanwhile.
Hello,
We've identified a possible root cause of the reconnection issue. The upcoming release (4.0.0) will include the fix.
Hello,
The release with the fix just been released. Feel free to open a new ticket if you face any issues.
Just captured this after upgrading to 3.0.0 Any suggestions?