fix: channel.state break on going to background

[isekovanic]

🎯 Goal

Fixes a very old and prominent issue we've had in the SDK where sometimes upon a very specific queue of actions messages would stop updating in real time.

The issue is well documented in the following issues:

• This GH issue
• This Zendesk ticket
• Many other scattered comments across other issues that I'm unable to find right now

Despite the oneliner fix, this issue was incredibly difficult to reproduce consistently - especially because typically it would manifest differently across different integrations.

The TL;DR version of it is:

• Whenever we put the app using the SDK in background (either through going to background, locking the phone or whatever) we close the WS connection due to various reasons (the ability to receive push notifications, not wanting to endlessly keep the connection alive for long etc)
• When this happens, we would preemptively mark all channels as "out of date" in the hope of them resyncing by default when we're back
• However, whenever coming back from BG this state would never be cleared and properly set
• Then, in various circumstances this particular check of the channel logic in our low level client would fail and so we'd never receive new messages, unable to recover unless we manually trigger loading to more recent messages or simply reload the app

Removing it is completely safe as we handle the resyncing of channels elsewhere.

🛠 Implementation details

🎨 UI Changes

iOS

Before	After

Android

Before	After

🧪 Testing

☑️ Checklist

• I have signed the Stream CLA (required)
• PR targets the develop branch
• Documentation is updated
• New code is tested in main example apps, including all possible scenarios
  • SampleApp iOS and Android
  • Expo iOS and Android

[Stream-SDK-Bot]

SDK Size

title	develop	branch	diff	status
js_bundle_size	452 KB	455 KB	+2624 B	🔴