Unreliable timeout in 1.1.0

[eLud]

I recently updated the Connect lib to 1.1.0 in an app, and was able to notice that the timeout specified in ProtocolClient and ProtocolClientConfig seems to not be working reliably. Are you aware of this?

I can't reproduce every time, but was still able to do it multiple times + had user feedback about it.

Step to reproduce:

• Set a timeout
• Set Network Link Conditioner on, with 100% Loss config
• Trigger the request

Outcome:

• The request never gets an answer, and Connect never didn't time out either.
• If you are awaiting for the result in a specific loading state, the app get stuck in this state

Expected behavior:

• The timeout fires consistently if no response is received after the specified time.

[aymericbeaumet]

@rebello95: do you have any insights on this? I'm wondering if this is only the top of the iceberg with potentially deeper ramifications.

[rebello95]

👋🏽 hey @aymericbeaumet and @eLud! Apologies - I did see this issue and thought I responded, but must've failed to save my comment 😓

I spent a bit of time trying to reproduce this but wasn't able to using the config in the screenshot above. Do either of you have tips for reproducing this or sample projects where it's happening for you consistently?

cc @eseay in case you've come across this as well