Skip to content

chore: merge develop into v10 - #3865

Merged
isekovanic merged 15 commits into
V10from
chore/merge-develop-into-v10
Oct 16, 2026
Merged

isekovanic merged 15 commits into
V10from
chore/merge-develop-into-v10

Conversation

@isekovanic

Copy link
Copy Markdown
Contributor

🎯 Goal

πŸ›  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

isekovanic and others added 15 commits October 8, 2026 16:01
## 🎯 Goal

This PR removes the pinned `@gorhom/react-native-bottom-sheet` version
as it is no longer needed.

Originally, the pin existed at all due to some inconsistencies with
other dependencies, which have now been long resolved upstream. Thus, we
remove the pin so that apps also relying on the bottom sheet no longer
have to have 2 versions installed (if they do not match `5.2.9`
specifically).

## πŸ›  Implementation details

<!-- Provide a description of the implementation -->

## 🎨 UI Changes

<!-- Add relevant screenshots -->

<details>
<summary>iOS</summary>


<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>


<details>
<summary>Android</summary>

<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>

## πŸ§ͺ Testing

<!-- Explain how this change can be tested (or why it can't be tested)
-->

## β˜‘οΈ Checklist

- [ ] I have signed the [Stream
CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform)
(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
fix: remove bottom sheet pinned version (#3849)
## 🎯 Goal

Deprecate the standalone `@stream-io/chat-react-native-ai` package and
ship the AI components from the SDK itself, the same way React did in
GetStream/stream-chat-react#3314.

This is a direct port of [this part of the AI components
repo](https://github.com/GetStream/ai-components-js/tree/main/packages/react-native-sdk),
with some minor tweaks and fixes.

Apps import them from a separate entry point:

- `stream-chat-react-native/ai-components`
- `stream-chat-expo/ai-components`

Apps that don't import it are unaffected: no extra JS in their bundle
(+61 bytes, one empty native-handler slot) and no new required
dependencies.

## πŸ›  Implementation details

**Port.** Markdown, syntax highlighting, charts, the AI composer and
dictation are ported 1:1. The only deliberate changes are:

- `ShimmeringView` is removed; the typing indicator uses the SDK's
native shimmer, laid over the text.
- If the dictation module isn't compiled in, the mic button hides itself
instead of crashing.
- `react-syntax-highlighter` moves to v16, for the Prism CVE.
- The native code is registered by the two wrappers instead of a
separate package.

**Isolation.** `validate-entry-isolation` (part of `yarn lint`) fails if
the main entry points ever reach the AI code or its dependencies. It
also fails if the AI entry reaches the chat SDK, so AI-only apps don't
bundle chat. Both directions are confirmed with real Metro bundles.

**Dependencies.** The JS-only libraries (zod, the highlighter,
simple-markdown, state-store) are regular dependencies. Skia and
victory-native are optional peers, needed only by apps that use the AI
components.

**Native.**

- **PerfText:** an Android Fabric text view with a C++ shadow node,
built through a custom CMakeLists in each wrapper.
- **AIDictation:** a TurboModule for both platforms.
- **iOS dictation is opt-in:** enable it with
`$StreamChatEnableDictation = true` in the Podfile, or with the new
`stream-chat-expo` config plugin. Referencing the Speech framework makes
App Store Connect require a speech-recognition purpose string from every
app, so it isn't compiled in by default.
- **Android:** the library never declares `RECORD_AUDIO`.

**Fixes on top of the port**, mostly bugs inherited from upstream:

- A final dictation result arriving after recording stops is now applied
to the input.
- Android no longer cuts users off mid-sentence when the recognizer
sends no live results.
- The iOS first press no longer races the permission prompts.
- Per-method lodash imports (-45.6 KB min) and direct
`react-syntax-highlighter` imports (-369 KB min), both in AI bundles
only.
- The native shimmer now links on RN 0.76 iOS (`StreamShimmerViewCls`),
an existing v9 issue.

**Samples.** SampleApp gets an "AI Assistant" screen. The Expo ChatGPT
sample from `ai-components-js` is ported as `examples/ExpoChatGPTSample`
(Expo 57).

**Migration.** See `package/src/ai-components/README.md`: the new import
path, the Podfile flag and plugin rename, the Babel plugin `zod` needs,
and the removed exports.

## πŸ§ͺ Testing

## 🎨 UI Changes

---------

Co-authored-by: Anton Arnautov <arnautov.anton@gmail.com>
## 🎯 Goal

<!-- Describe why we are making this change -->

## πŸ›  Implementation details

<!-- Provide a description of the implementation -->

## 🎨 UI Changes

<!-- Add relevant screenshots -->

<details>
<summary>iOS</summary>


<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>


<details>
<summary>Android</summary>

<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>

## πŸ§ͺ Testing

<!-- Explain how this change can be tested (or why it can't be tested)
-->

## β˜‘οΈ Checklist

- [ ] I have signed the [Stream
CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform)
(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
## 🎯 Goal

Fixes
[#3860](#3860).

Linear ticket:
https://linear.app/stream/issue/RN-444/issues-with-chat-overlays-in-modals

A chat rendered inside a native modal (for example a `react-navigation`
`fullScreenModal`) needs its own `OverlayProvider`, because on iOS the
root one is rendered in a different view controller, behind the modal.
With a second `OverlayProvider` mounted, the message overlay of the root
chat breaks once the modal is closed.

Every `MessageOverlayHostLayer` shares two pieces of state. One is the
shared value controller in `message-overlay-store.ts`. The other is the
set of portal host names (`message-overlay`, `top-item`, `bottom-item`
and the closing slots), which `react-native-teleport` keeps in a single
native registry per process. In both cases the last registration wins,
and unregistering removes the entry instead of restoring the previous
one. After the modal's provider unmounted, the root provider was left
without a controller and without registered hosts.

This PR makes sure several `OverlayProvider`s mounted at the same time
work, without changing the existing public API.

## πŸ›  Implementation details

- The shared value controller is now a stack.
`registerOverlaySharedValueController` keeps its signature, and
unregistering hands control back to the previously registered
controller. It's pretty much the same "trick" used for the
`PortalWhileClosingView` stack.
- Every `OverlayProvider` creates an id and registers its
`MessageOverlayHostLayer` on a host layer stack. The most recently
mounted layer is the top one and owns the overlay.
- A host layer that is not the top one stays mounted and treats the
overlay as inactive, so it renders no backdrop, adds no back handler and
never finalizes the close. It parks its portal hosts under names unique
to it (`<name>:<layerId>`, closing slots included) and takes the shared
names back once it becomes the top one again. The hosts are renamed
instead of unmounted, because remounting them lets Fabric reuse a
recycled `PortalHostView`, which might keep stale sizes. Of course we
could work around this and still let stuff remount but it's also
arguably breaking since we have configurable parts of the DOM tree in
there (and those parts would start remounting rather than just
rerendering).
- A custom `MessageActions` renders its own hosts with the shared names,
so only the top layer renders it.
- `PortalWhileClosingView` reads the id of its provider from a new
internal `OverlayHostLayerContext` and only measures and teleports while
that provider is the top one.

With a single `OverlayProvider` the stack has one entry and every code
path should behave exactly as before.

Note: This entire process is meant to solve specifically usecases like
modals, which fire up their own `ModalViewController` instance and
essentially break. Due to the limitations of refcounting providers in
order to determine their ID, having something like 2 `OverlayProvider`s
side by side would not really work (whichever one gets registered
**later** wins). This fixable, but of course breaking as the api itself
would have to be tied to a dedicated `OverlayProvider` (and could no
longer be used from the direct exports). It is something I'll consider
for V10, if there is time but otherwise we'll stick to this for the time
being.

## 🎨 UI Changes

<details>
<summary>iOS</summary>


<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>


<details>
<summary>Android</summary>

<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>

## πŸ§ͺ Testing
/

## β˜‘οΈ Checklist

- [ ] I have signed the [Stream
CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform)
(required)
- [x] PR targets the `develop` branch
- [ ] Documentation is updated
- [ ] New code is tested in main example apps, including all possible
scenarios
  - [x] SampleApp iOS and Android
  - [ ] Expo iOS and Android
## 🎯 Goal

Since it would appear our MacOS CI runners are running a bit dry, we'll
stop running them on every branch commit with this PR.

They'll still run to deploy the sample apps to Testflight/Firebase
Distribution on commits to `develop`/`main` and we'll run them manually
on every branch when it's actually needed.

## πŸ›  Implementation details

<!-- Provide a description of the implementation -->

## 🎨 UI Changes

<!-- Add relevant screenshots -->

<details>
<summary>iOS</summary>


<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>


<details>
<summary>Android</summary>

<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>

## πŸ§ͺ Testing

<!-- Explain how this change can be tested (or why it can't be tested)
-->

## β˜‘οΈ Checklist

- [ ] I have signed the [Stream
CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform)
(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
## 🎯 Goal

<!-- Describe why we are making this change -->

## πŸ›  Implementation details

<!-- Provide a description of the implementation -->

## 🎨 UI Changes

<!-- Add relevant screenshots -->

<details>
<summary>iOS</summary>


<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>


<details>
<summary>Android</summary>

<table>
    <thead>
        <tr>
            <td>Before</td>
            <td>After</td>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>
                <!--<img src="" /> -->
            </td>
            <td>
                <!--<img src="" /> -->
            </td>
        </tr>
    </tbody>
</table>
</details>

## πŸ§ͺ Testing

<!-- Explain how this change can be tested (or why it can't be tested)
-->

## β˜‘οΈ Checklist

- [ ] I have signed the [Stream
CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform)
(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

Copy link
Copy Markdown
Contributor

SDK Size

title develop branch diff status
js_bundle_size 2036 KB 2017 KB -19214 B πŸš€
ai_components_size 130 KB 130 KB 0 B 🟒

@isekovanic
isekovanic merged commit c994ffd into V10 Oct 16, 2026
2 checks passed
@isekovanic
isekovanic deleted the chore/merge-develop-into-v10 branch October 16, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants