@opencx/widget-react-headless 5.7.0 → 5.7.1

package/README.md

@@ -86,9 +86,19 @@ import { fetch as expoFetch } from 'expo/fetch';
 ```
 
 1. `streamingFetch`: React Native's built-in fetch cannot read a response
-   while it arrives. Every other request keeps using the global fetch.
-2. Globals the stream reader uses: `structuredClone` and `TextDecoderStream`.
-   Install polyfills for them at startup, before the widget is imported.
+   while it arrives. Expo SDK 57 installs `expo/fetch` as the global fetch
+   (unless `EXPO_PUBLIC_USE_RN_FETCH` is set), so there `streamingFetch` can
+   be left out. Every other request keeps using the global fetch. If you wrap
+   `expoFetch` (to add headers or logging), return its response unchanged.
+   React Native's global `Response` has no readable body, so the widget
+   cannot read a response rebuilt with `new Response(...)`. It then reads the
+   reply again through the global fetch and logs a warning once; where the
+   global fetch cannot stream either, the reply appears once it is saved.
+2. Globals: the widget needs `crypto.getRandomValues`, which React Native does
+   not provide. Install `react-native-get-random-values` and import it first
+   in your entry file. The stream reader also uses `structuredClone` and
+   `TextDecoderStream`; Expo SDK 57 has both, and older runtimes need
+   polyfills installed at startup, before the widget is imported.
 3. Resuming a dropped reply: browsers resume when the tab is visible again or
    the network returns. React Native has neither event, so call
    `useAgentChatUi().resumeInterruptedTurn()` when `AppState` becomes