[isekovanic]

Tickets:

• https://linear.app/stream/issue/REACT-1486
• https://linear.app/stream/issue/REACT-1487
• https://linear.app/stream/issue/REACT-1489
• https://linear.app/stream/issue/REACT-1490

🎯 Goal

Fixes for the must-have V10 issues from the board triage. Each commit fixes one ticket.

Commit	Ticket	Fix
a0354684c	REACT-1486	Regression test for an optimistic edit of an auto-translated message
b5705f953	REACT-1489	setupCommandUIMiddlewares no longer inserts duplicate middleware
b0d28db84	REACT-1490	A channel list loads its first page even when an event already added channels to it
7a0376993	REACT-1487	Reopening a channel or thread left on an older page shows the newest messages

🛠 Implementation details

REACT-1486 - optimistic edit of a translated message

Commit: a0354684c

The fix is in stream-chat-js (GetStream/stream-chat-js#1975). This commit adds the RN regression test, which edits an auto-translated message through the composer and checks the rendered row while the request is in flight. It fails until stream-chat is bumped to an rc that includes GetStream/stream-chat-js#1975.

REACT-1489 - duplicate command middleware

Commit: b5705f953

setupCommandUIMiddlewares inserts four middleware but passed unique: true only on the first. The composer setup function runs again whenever the composer subscribes, which happens every time a channel opens, and on every client.config change. The draft command injection, the active command guard and the command string extraction piled up as a result. Each copy of the draft injection prepends the command, so a draft saved with an active command came out as /giphy /giphy cats.

All four inserts now pass unique: true, so running the setup again replaces them.

REACT-1490 - channel list stuck on channels an event added

Commit: b0d28db84

ChannelManager.ingestChannel() puts a channel into every matching paginator, including one that was never queried. usePaginatedChannels treated a list as unloaded only while channels === undefined, and loadNextPage refuses a paginator that was never queried. A list that mounted after an event reached its paginator showed only those channels until pull-to-refresh. That happens when the app opens a channel from a push notification and the user goes back to the list, or with a second list, such as archived channels, that mounts later.

A paginator that was never queried now counts as unloaded too, so the list runs its first query. The offline DB seed and a failed first query both mark the paginator as queried, so neither causes an extra query.

REACT-1487 - reopening a channel or thread on an older page

Commit: 7a0376993

The paginators of a channel and a thread outlive the screen. After a jump to a quoted, pinned or searched message, reopening the channel or thread showed that older page. <Channel> relied on watch() to go back to the newest messages, but watch() returns early for a channel that is already watched and loaded since GetStream/stream-chat-js#1943. v9 re-watched on open and landed on the newest messages.

The new public useJumpToLatestOnOpen() hook calls jumpToTheLatestMessage() when a channel or thread opens on an older page. The newest page is normally still loaded, so this switches back locally without a request. It does nothing when a jump already landed or is in flight, so a deep link from the screen still lands on its target. It also does nothing when <Channel> is about to jump to the first unread message, or with initializeOnMount={false}. It runs in a layout effect so the old page isn't painted first, and its dependencies are stable, so it runs once per open.

ChannelShell runs the hook from an empty JumpToLatestOnOpen component under its providers, the same way it renders NotificationAnnouncer. That covers <Channel>, <Thread> and any message list, including custom ones. ChannelShell takes initializeOnMount as an internal prop that <Channel> passes on. The hook is exported for apps that set initializeOnMount={false} and still want this behaviour.

The MessageList in a thread test setup now seeds replies with setItems(), the way a thread seeds latest_replies. It used to write items straight into the paginator state, which leaves no intervals and looked like a list that isn't showing its newest page.

🎨 UI Changes

None.

🧪 Testing

• Running setupCommandUIMiddlewares three times on one composer leaves one of each middleware. Without the fix there are three.
• A ChannelList whose paginator got a channel from ingestChannel() before it was queried runs its first query on mount and shows the queried page. Without the fix it never queries.
• Channel tests cover reopening on an older page, a deep link that already landed, a jump in flight, initializeOnMount={false} and the first unread jump. Thread tests cover the first three. Without the fix, only the two reopening tests fail.
• In SampleApp on iOS, reopening a channel after a search deep link and reopening a thread after jumping to a quoted reply both land on the newest messages, and the deep link still lands on its target. Opening threads normally triggers no jump and no request.
• The full unit suite, yarn test:typecheck, eslint, prettier and yarn build pass, apart from the REACT-1486 test above.

☑️ 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	2037 KB	2022 KB	-16015 B	🚀
ai_components_size	163 KB	163 KB	-16 B	🚀