Still seeing #2840 about stream-chat-swift HOT 5 CLOSED

we were using develop of stream-chat-swift, i've just changed to using 4.47.0, so i can also report back in about a week to say whether it was just a versioning thing

from stream-chat-swift.

Hi @AndrewSB, unfortunately, we do not see this on our side, nor getting any other complaints about the AuthenticationRepository deadlock. Please do let us know if you'll find out that it was just a versioning thing.

Best,
Alexey

from stream-chat-swift.

Hi @AndrewSB, how do you know it is a deadlock based on the error? 🤔 From the image above, the Timout Error just means that the request timed out. It could just be a bad network from the user, etc.

from stream-chat-swift.

at the bottom of the screenshot above, i highlighted the error message. you can see mentions AuthenticationRepository:266 as the source of the error.

looking at that file, it looks like that WaiterTimeout comes from your auth repository failing to get an auth token:

does that all seem right? if so, i'll dig a little deeper and see if i can spot anything else for you

from stream-chat-swift.

Hi @AndrewSB , yes that is fine, some requests can timeout. Before, while timing out, they were deadlocking. That was a problem, but it should not happen anymore.

Feel free to re-open the issue if you can reproduce the timeout error and deadlock again 👍

from stream-chat-swift.