@ethora/chat-component-rn 26.5.7 → 26.5.10

package/CHANGELOG.md

@@ -3,6 +3,139 @@
 All notable changes to `@ethora/chat-component-rn` are listed here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this project doesn't follow strict semver yet — version corresponds to the `package.json` field.
 
+## [26.5.10]
+
+Lifecycle hardening on top of 26.5.9, driven by live on-device testing: a full reconnect-after-loss overhaul (a live test surfaced — and this release fixes — a reconnect storm), cache no longer wiped on re-entry, automatic AppState-driven unread visibility plus a new `isVisible` prop for tab hosts, `initBeforeLoad` auto-retry, and the "New messages" divider polish. Full regression sweep — typecheck clean, 583 jest tests green.
+
+### Fixed
+
+#### Connectivity / reconnect (the big one)
+
+- **Never permanently gives up.** `scheduleReconnect` used to hard-stop at `maxReconnectAttempts` (5) — ~62s, after which only a NetInfo/foreground event could revive the client. It now retries indefinitely while mounted, with the exponential backoff **clamped to `maxReconnectDelay` (30s)**.
+- **Connect-time failures retry.** A failed `client.start()` lands in `status: 'error'`, which previously had no retry path (only a drop *after* being online did). It now schedules a backoff reconnect (refreshing creds first on a SASL `not-authorized`).
+- **Reconnect storm fixed (found by the live bad-host test: 397 schedule calls / 0 actual reconnects / 3 orphan clients).** Three causes addressed: (a) the `initBeforeLoad` auto-retry no longer leaves orphan `XmppClient` instances — `initializeClient` closes the prior global client before creating a new one; (b) `scheduleReconnect` now coalesces — a burst of `disconnect` events no longer re-arms the timer faster than it can fire (which starved `reconnect()` and spammed the counter); (c) **`@xmpp/client`'s built-in reconnect is disabled** so this SDK is the single reconnect driver (no dual-layer ~1s socket storm against a dead host).
+- **`forceReconnect` debounced (2s)** so NetInfo + AppState + the new watchdog firing together can't spawn a storm.
+- **New foreground watchdog.** While the app is active, a 30s timer forces a reconnect when the client isn't online and reconnect isn't suppressed — covering a stuck `connecting`/`error` and server-side outages NetInfo never reports. Replaces the old provider reconnect effect, which keyed on `client.status` (a mutated class field React doesn't track) and so frequently never re-ran.
+- **NetInfo reconnect loosened.** Forces a reconnect on any "reachable while offline/error", not only after a prior offline→online transition — a missed/coalesced offline event no longer strands the client.
+
+#### initBeforeLoad
+
+- **Auto-retries a transient bootstrap failure** up to 3× with backoff before surfacing the error modal (a flaky network at launch self-heals; auth/credential failures still fail fast).
+- **Overall 45s time budget** — a hung step can no longer strand the loader in `running` forever.
+- **Private store re-synced on reconnect** (not just MUC re-join), so unread / `lastViewedTimestamp` stays accurate after a long reconnect.
+
+#### Unread tracking
+
+- **Re-entry no longer wipes the cache.** History is now **merged by message id** (the microsecond-resolution stanza id) instead of replaced — older cached messages and the unread derived from them survive; only a true gap (the fetched page shares no id with the cache) clears that one chat's cache. `addRoom` also preserves cached messages + unread when the `/chats/my` refetch omits them (it sends `messages: []`).
+- **AppState now drives room visibility automatically** (library-level). Backgrounding stamps `lastViewedTimestamp = now` and clears the open room's "visible" state — so messages arriving while away count as unread instead of being silently marked read; foreground restores it. No consumer wiring required.
+- **New `<Chat isVisible={…} />` prop.** For hosts that keep `<Chat>` **mounted while hidden** (tab/route navigators), pass `isVisible={currentTab === 'chat'}` — the library clears/restores room visibility from it internally, so consumers never reach into the store. Complements `useChatRoomFocus`.
+
+#### "New messages" divider
+
+- **White text.** The label sits on a dark pill but rendered in the (often blue) primary color — unreadable. It's now white.
+- **Removed when you leave the chat** (tab switch / navigation / app background) and **spliced out rather than tombstoned**, so it correctly re-appears for the next batch of unread — previously it was a one-shot (the tombstone blocked every future divider).
+
+#### Misc
+
+- **Benign unhandled-rejection red box gone.** The dev rejection tracker now reports only *genuinely* unhandled rejections (`allRejections: false`), and `createTimeoutPromise` self-observes its timeout so a settled `Promise.race` no longer leaks a `reject(undefined)`.
+- **Input bar spacing.** The send button's horizontal margin is removed so its gap from the input matches the attach button's.
+
+### Tests / internal
+
+- Testbed harness (`AppLoginChatsRn`): opens on the **Setup** tab by default; runtime credentials moved to a **gitignored** local file (no secrets in tracked source — `DEFAULT_CREDS` is blank, `seed-jwt-creds.example.json` carries placeholders); LogBox dev-noise filtered via `setupLogBox`; a `METRO_NO_WATCHMAN=1` escape hatch in `metro.config.js` for flaky watchman.
+- New regression tests: reconnect coalesce + `forceReconnect` debounce + uncapped/clamped backoff, history merge / gap-clear / no-wipe, `addRoom` preservation, and the divider splice. Full sweep — typecheck clean, **583 jest tests** green.
+
+## [26.5.9]
+
+Hardening round on top of 26.5.8: the critical reconnect/MUC delivery bug, unread-tracking gaps in tab navigators, a stale-JWT idle loop, translated-message reconciliation, and the `expo-av → expo-video` migration for video playback. Full regression sweep — typecheck clean, 554 jest tests green.
+
+### Fixed
+
+#### Connectivity (the critical one)
+
+- **Bug #21 — reconnect didn't re-join MUC rooms (local double-tick, never delivered).** On a new stream after an extended drop the client was no longer joined to any room, so sends got a local double-tick but never reached the other end. `XmppClient` now fires an `onOnline` callback that the provider wires to `allRoomPresences(...)` — every room's presence is re-sent on reconnect. Reconnect is also single-flight guarded (no leaked concurrent clients), detaches the old client's listeners before re-init, and tracks the reconnect timer so logout can cancel it.
+- **Bug #21 (race) — `presencesReady` never reset on disconnect.** The flag stayed `true` across a drop, so (a) the heap sender could fire into a dead socket and (b) the `false→true` transition that flushes offline-queued messages never re-armed on reconnect. `onDisconnect` now resets `presencesReady = false`; on reconnect `onOnline` flips it back `true` only after `allRoomPresences` has synchronously re-sent presence — queued messages flush after the re-join, not before.
+- **Idle stale-JWT loop (follow-up to #17).** When a JWT expired during idle and the credential refresh produced no new password, the client used to retry forever with stale creds (`not-authorized` loop). It now detects two consecutive no-progress refreshes, latches `authExpired`, suppresses further reconnects, and emits an `ethora:authExpired` DeviceEventEmitter event so the host can re-authenticate (e.g. re-mount `<Chat>` with a fresh `jwtLogin.token`). `ethora:retryBootstrap` clears the latch.
+- **Bug #4 (residual) — fire-and-forget `client.send()` leaks.** A global send wrapper attaches a no-op `.catch` to every underlying send promise (while returning the same promise to awaiting callers), so a send that rejects during socket teardown no longer surfaces as `Uncaught (in promise)`.
+
+#### Unread tracking
+
+- **Bug #19 — `useUnread()` stuck at 0 in tab navigators.** When `<ChatRoom>` stays mounted across tabs, blur never released the active-room marker, so the unread middleware treated the room as "always being viewed". `useChatRoomFocus` now releases the active room (`setCurrentRoom({ roomJID: null })`) and stamps `lastViewedTimestamp` on blur — counting resumes the moment the user leaves the tab.
+- **Bug #20 — scroll-to-bottom badge inflated by loading older history.** The badge now snapshots the newest message timestamp when you leave the bottom and counts only messages newer than that snapshot, so back-pagination (load-more) of older messages can never bump the count.
+- **Cold-start badge — incoming `lastViewedTimestamp: 0` clobbered the persisted marker.** `addRoom` now ignores an incoming `0` placeholder (the stanzaHandlers default) and preserves the hydrated/persisted value, so badges are correct on first paint after a cold start.
+
+#### Messaging
+
+- **Translated / resent messages stuck pending + duplicated.** `sendTextMessageWithTranslateTagStanza` didn't forward a client message id, so translated sends (and every resend that took the translate path) went out without an id — the server echo arrived with a different id and never reconciled with the optimistic bubble (stuck "pending" + a duplicate). It now accepts and forwards `customId`; `useHeapSender` and `resendMessage` pass it.
+
+#### UI / customization
+
+- **Bug #14 — delete confirmation is now a small centered dialog with a white action label.** Confirm-style modals render in a dedicated bounded `compactDialog` view (never full-screen), and the filled (e.g. red Delete) button now passes `color="#FFFFFF"` explicitly so the label isn't black-on-red.
+- **Bug #13 — context-menu placement is now measured, not estimated.** `MessageInteractions` measures the rendered menu height via `onLayout` and places the menu just above/below the message's actual bounding box, clamped to the viewport — the menu sits adjacent to the message instead of floating far above it.
+- **New `config.disableConnectionErrorOverlay`.** Swaps the full-screen "Connection error" overlay for a small non-blocking `ConnectionBanner`, so a transient reconnect doesn't take over the whole screen.
+- **Android context menu polish.** Hairline dividers (instead of an all-sides border that rendered badly on Android) and explicit row label styling (`includeFontPadding: false`) so menu rows match iOS.
+
+#### Media
+
+- **`expo-av → expo-video` migration for video.** `VideoMessage`, `FilePreviewModal`, and `MediaFilePreview` now use `expo-video` (`useVideoPlayer` / `VideoView`); the inline bubble shows a tappable poster that opens the full-screen player. **`expo-video` is now a peer dependency** — run `npx expo install expo-video`. Audio still uses `expo-av`.
+
+### Tests / internal
+
+- Added regression tests: unread cold-start + tab focus/blur, `useUnread` perturbations, the `presencesReady` online/disconnect cycle, and the JWT-login bootstrap mock now stubs `setOnOnline` / `setOnAuthExpired`.
+- Repaired stale tests that lagged source changes (apiClient token getters, `onGetLastMessageArchive(stanza, xmppWs)`, `createRoom` arity) and re-pointed the package-shape test at the `exports` map (the field consumers actually resolve), since the repo root doubles as the Expo testbed and `main` must stay `index.js`.
+
+## [26.5.8]
+
+Follow-up to 26.5.7 covering the customer-retest list — every "Not in 26.5.7 / Worsened" item, plus a usability gap in `useUnread` and a new scroll-to-bottom UX affordance.
+
+### Fixed
+
+#### Media (the long tail of bug #10 and #9)
+
+- **Bug #10 — `/files/` 500 retries with singular field name.** Removing the manual Content-Type header in 26.5.6 wasn't enough — some Ethora deployments expect the field name `file` (singular) instead of `files` (plural). The plural form works for image uploads via permissive server sniffing but rejects video/audio/docs with 500. `useSendMessage.sendMedia` now: (a) coerces iOS `assets-library://` URIs to `file://` so RN's FormData polyfill builds a real multipart blob, then (b) tries `files` (plural — current SDK default), and (c) on 500 retries with `file` (singular). Also surfaces `serverBody` / `fileBlob` shape in the diagnostic log for any remaining 500s.
+- **Bug #9 — video controls hidden behind tab bar; audio preview blank.** `FilePreviewModal`: video player now sits inside a wrapper with `paddingBottom: 80` so the `useNativeControls` overlay clears the host app's tab bar + iOS home indicator. New `audio/*` switch case renders the existing `AudioMessage` (expo-av) component inside an info card with filename — audio messages from other users are now actually playable in the preview.
+
+#### Sending / send-state
+
+- **Bug #18 — silent send failures stuck on "sending..." forever.** Send paths (`sendMessage` + `sendMedia` in `useSendMessage`) now arm a 30-second watchdog after the optimistic bubble lands. If no server echo arrives in that window AND the message wasn't already explicitly marked failed by the catch path, the watchdog flips it to "Failed — tap to retry". Covers the no-internet case where XMPP buffers the send without throwing.
+
+#### UX
+
+- **Bug #6 — Android keyboard blocking the chat input + flicker.** 26.5.7's `behavior={undefined}` on Android broke hosts that disable `adjustResize` via `softInputMode`. Reverted to `behavior="padding"` on both platforms — padding adds bottom-padding equal to the keyboard height without changing layout height, so no double-resize (no flicker) and the input is always lifted regardless of the host's softInputMode.
+- **Bug #13 — context menu overcorrected too high.** The 26.5.7 `MENU_HEIGHT=280` over-estimate (based on a phantom reactions strip) forced the menu above the bubble even when there was room below. Real `MessageInteractions` is 1-3 rows × ~40px (40 for non-own, ~140 for own). Lowered to 160; the prefer-below path now wins for normal cases and only switches to above when the bubble genuinely lacks bottom space.
+- **Bug #14 — delete confirmation still full-screen.** The 26.5.7 `compact` style used `height: 'auto'` which RN doesn't honour — the styled-component's `height: 100%` won. Replaced with `height: undefined` + `minHeight: 0` + `alignSelf: 'center'`. Now a properly small (max 360 wide) centered dialog.
+
+#### Promise hygiene (bug #4 part 2 — exhaustive sweep)
+
+The `(in promise, id: 0)` and `(in promise, id: 2)` red screens were not all in `useChatWrapperInit`. An exhaustive sweep across `src/` found and patched:
+
+- `ChatWrapper.tsx` — the outer `await initializeClient(...).then(c => {...})` callback had no `.catch()`. Converted to `await` + inner try/catch.
+- `ChatWrapper.tsx` — three fire-and-forget `refresh()` calls (legacy / storedClient / provider branches) — wrapped each with `.catch((err) => console.warn('refresh failed', err))`.
+- `usePushNotifications.ts:81` — `getInitialNotification().then(...)` without `.catch()` — added one.
+- `usePushNotifications.ts:54` — `initToken()` was fire-and-forget in the bootstrap `useEffect`; any sync throw before the inner try-block leaked. Added `.catch`.
+- `networking/xmpp/getRoomsPaged.xmpp.ts` — **the most likely id:0/id:2 culprit.** `client.send(message)` was NOT awaited inside an `async` Promise executor, so when the socket was closing during reconnect, the send rejection escaped the try/catch entirely. Rewrote without the async executor, captured the send promise, attached `.catch` synchronously, and rewrote the timeout chain to attach its rejection handler at construction time (no race).
+- `networking/xmpp/presenceInRoom.xmpp.ts` — same `new Promise(async (resolve, reject) => …)` anti-pattern with a racy `.catch(reject)` on the timeout. Rewrote to use a regular promise constructor + an inner async IIFE that explicitly funnels every failure path through `reject()`.
+
+Also installed a **dev-only global unhandled-rejection tracker** (`src/utils/installPromiseRejectionTracker.ts`, mounted from `ReduxWrapper`) that catches any future leaks and prints the actual rejection value + stack to Metro logs (works on Hermes via `HermesInternal.enablePromiseRejectionTracker` and on the standard `unhandledrejection` event). No-op in production builds. If a new red-screen ever appears, the integrator now sees exactly where it originates.
+
+#### Media preview (bug #9 — true inline preview)
+
+`FilePreviewModal` now renders office docs (DOC / DOCX / XLS / XLSX / PPT / PPTX / TXT / CSV / RTF) inline via a new `DocumentViewer` component that embeds Google's free `docs.google.com/gview?url=…&embedded=true` viewer in a `react-native-webview`. The previous default case showed only an info card; for these MIME types the user now sees the actual document content. PDF keeps its existing local-download-then-WebView path (`PdfViewer`). Truly unrenderable binary types still fall through to the info card with filename + download prompt.
+
+### Added
+
+- **`useChatRoomFocus({ roomJID, isFocused })` hook** — public unread-tracking hook for tab-based navigators where `<ChatRoom>` never unmounts. Mirrors the mount/unmount lifecycle internally — focus stamps `lastViewedTimestamp = 0` (clears badge, marks active room), blur stamps `Date.now()` (so future messages count). Eliminates the consumer workaround of importing `store` / `setLastViewedTimestamp` / `setCurrentRoom` from internal `src/` paths.
+- **Unread-count badge on the scroll-to-bottom arrow.** When the user is scrolled up and new messages arrive, the down-arrow now shows a count chip (capped at `99+`). Resets when they scroll back to the bottom.
+- **New granular config flags** for member-list actions (bug #16 done right this time):
+  - `disableMemberProfileActions?: boolean` — hide the whole action block.
+  - `hideMemberSendMessageAction?: boolean` — hide only "Message".
+  - `hideMemberCopyIdAction?: boolean` — hide only "Copy User Id".
+
+### Changed
+
+- **Reverted 26.5.7 widening of `disableProfilesInteractions`.** It now controls message-list avatar taps only (its original scope) — the new granular flags above handle the chat-info member actions per-button instead of all-or-nothing.
+- **`roomsSlice.addRoom` cold-start fix.** The previous `Date.now()` default for `lastViewedTimestamp` (used when the payload didn't carry one and there was no existing room) stamped a "now" marker that made messages sent while the app was killed look already-read on next launch. Now anchors to the newest message in the payload (so already-loaded history is "seen" but anything strictly newer counts as unread), falling back to `0` only when there are no messages yet (lets the private-store hydration set the real marker).
+
 ## [26.5.6]
 
 Closes the open items from the 26.5.5 customer bug tracker plus seven new ones (uploads, media preview, XMPP idle recovery, send failures, UI polish, customization gates). One existing config flag (`disableProfilesInteractions`) gets its semantics widened — everything else is additive.

package/README.md

@@ -15,6 +15,8 @@ React Native chat UI + chat core for iOS and Android, powered by the Ethora plat
 - [Configuration](#configuration) — full `IConfig` reference in [instructions.md](instructions.md)
 - [Authentication modes](#authentication-modes)
 - [Pinning a single room](#pinning-a-single-room)
+- [Unread tracking in tab-based hosts](#unread-tracking-in-tab-based-hosts)
+- [Customization flags worth knowing](#customization-flags-worth-knowing)
 - [Quality & test coverage](#quality--test-coverage)
 - [Local development](#local-development)
 - [Changelog](CHANGELOG.md)
@@ -42,7 +44,7 @@ The package defaults to the canonical Ethora Cloud endpoints:
 | Web / sign up | `https://app.chat.ethora.com` |
 | Swagger / API docs | `https://api.chat.ethora.com/api-docs/#/` |
 
-To target QA, point the equivalent props/env vars at `chat-qa.ethora.com`. To self-host, override with your own `xmppSettings` and `baseUrl` — see the example below.
+To target a QA or staging environment, point the equivalent props/env vars at that environment's API + XMPP hosts. To self-host, override with your own `xmppSettings` and `baseUrl` — see the example below.
 
 ## Install
 
@@ -66,10 +68,12 @@ Image / video / document / audio send & receive, HEIC→JPEG conversion, profile
 
 ```bash
 npx expo install \
-  expo-av expo-clipboard expo-document-picker \
+  expo-av expo-video expo-clipboard expo-document-picker \
   expo-image-manipulator expo-image-picker expo-media-library
 ```
 
+> Video playback uses **`expo-video`** (`useVideoPlayer` / `VideoView`); `expo-av` is still used for audio. Install both.
+
 > No `metro.config.js` shim is required. As of `26.5.5` the SDK no longer statically imports any legacy `react-native-*` native modules; the bundled `withEthoraShims` helper is preserved as a no-op for backward compat with older setups.
 
 ### 3. iOS pods
@@ -202,6 +206,59 @@ The complete field-by-field reference — every option in `IConfig`, grouped by
 />
 ```
 
+## Unread tracking in tab-based hosts
+
+`useUnread()` and the room-list badge are wired to the `<ChatRoom>` mount/unmount lifecycle by default, and **app background/foreground is handled automatically** — backgrounding stamps "read up to now" and clears the open room's "viewed" state (so messages that arrive while you're away count as unread instead of looking already-read); foreground restores it. No wiring needed for that.
+
+What the SDK *can't* see on its own is an in-app **tab/route switch** where the chat screen **stays mounted while hidden** — there the lifecycle never fires and the room looks "always viewed". Signal it one of two ways (don't reach into the store):
+
+**Option A — the `isVisible` prop (simplest):**
+
+```tsx
+function ChatTab({ currentTab }: { currentTab: string }) {
+  // Library clears/restores the room's unread state from this flag.
+  return <Chat config={{...}} isVisible={currentTab === 'chat'} />;
+}
+```
+
+**Option B — the `useChatRoomFocus` hook** (drive it from a navigator focus signal):
+
+```tsx
+import { useIsFocused } from '@react-navigation/native';
+import { Chat, useUnread, useChatRoomFocus } from '@ethora/chat-component-rn';
+
+function ChatTab() {
+  const isFocused = useIsFocused();
+  // Focus marks the room visible (clears the badge in-memory).
+  // Blur stamps `Date.now()` so future messages count as unread.
+  useChatRoomFocus({
+    roomJID: 'general@conference.xmpp.chat.ethora.com',
+    isFocused,
+  });
+  return <Chat roomJID="general@conference.xmpp.chat.ethora.com" config={{...}} />;
+}
+
+function TabBar() {
+  const { totalCount } = useUnread();
+  return <Badge count={totalCount} />;
+}
+```
+
+(If instead you **unmount** `<Chat>` when it's hidden, you need neither — mount/unmount already handles it.)
+
+Full details (including the cold-start fix and the scroll-to-bottom unread chip) live in [`docs/unread-tracking.md`](docs/unread-tracking.md).
+
+## Customization flags worth knowing
+
+| Flag | What it does |
+| --- | --- |
+| `disableChatHeaderBurgerMenuIcon` | Hides the burger icon in the chat header (the icon that opens the room-list dropdown). `chatHeaderBurgerMenu` controls only the dropdown — set this when you want neither rendered. |
+| `disableMemberProfileActions` | Hides the whole "Message / Copy User Id" action block in the chat-info member modal. Use when no per-user actions are appropriate (e.g. patient-facing apps). |
+| `hideMemberSendMessageAction` | Hides only the "Message" button, keeps everything else. |
+| `hideMemberCopyIdAction` | Hides only the "Copy User Id" button, keeps everything else. |
+| `disableConnectionErrorOverlay` | Replaces the full-screen "Connection error" overlay with a small, non-blocking `ConnectionBanner`. Set this when a transient reconnect shouldn't take over the whole screen. |
+| `eventHandlers.onMessageRetry` | `(event) => void` fired when the user taps the "Failed — tap to retry" indicator on a stuck send. Use for telemetry / surfacing a retry banner. |
+
 ## Quality & test coverage
 
 ### Jest (unit + integration)
@@ -210,7 +267,7 @@ The complete field-by-field reference — every option in `IConfig`, grouped by
 npm test          # ~2s, full suite
 ```
 
-45 files, 486 tests cover the SDK's substantive surface:
+54 files, 583 tests cover the SDK's substantive surface:
 
 | Layer                          | Coverage |
 |--------------------------------|----------|
@@ -234,7 +291,7 @@ npm run e2e:android        # ditto Pixel_6
 Uses any profile in `~/.ethora/profiles.json` (the same file the
 `@ethora/setup` CLI writes to). The runner logs the test user via
 REST, seeds the testbed's AsyncStorage with the resolved Creds, and
-exercises the full pipeline against a real tenant:
+exercises the full pipeline against a real environment:
 
 > REST login → AsyncStorage persisted Creds → app boot →
 > `/chats/my` → XMPP WebSocket → MUC presence join → MAM history →
@@ -245,9 +302,9 @@ single high-signal smoke for the most-likely class of regressions
 (auth flow, XMPP transport, room hydration).
 
 ### Live deep test
-A documented session log + screenshots from a side-by-side
-alice/iOS ↔ bob/Android run against chat-qa.ethora.com lives at
-`docs/260517_deep-test-chat-qa.md`. Useful as a reproducer recipe.
+A generic deep-test runbook for side-by-side iOS ↔ Android validation
+lives at `docs/deep-test-chat-runbook.md`. Use it as a reproducible
+checklist for your own QA environment.
 
 ### Bugs surfaced + fixed (full history on PR #4)
 The test pass surfaced a handful of latent bugs that had been
@@ -272,8 +329,8 @@ silently shipping. All fixed in the same branch:
 This repo doubles as an Expo testbed app: `App.tsx` mounts
 `AppLoginChatsRn`, a 3-tab (Setup / Chat / Logs) shell that drives the
 SDK end-to-end via either paste-a-JWT or email + app-token login. Run
-it against the canonical Ethora Cloud endpoints, your QA tenant, or a
-self-hosted Ethora instance — all configurable from the Setup tab at
+it against the canonical Ethora Cloud endpoints, your QA/staging
+environment, or a self-hosted Ethora instance — all configurable from the Setup tab at
 runtime.
 
 ### Prerequisites
@@ -384,7 +441,7 @@ export PATH="$PATH:$HOME/.maestro/bin"
 Run against an already-built + installed app + a booted simulator:
 
 ```bash
-# Default profile "mychatapp QA", room "Main chat"
+# Uses the first profile from ~/.ethora/profiles.json, room "Main chat"
 npm run e2e:ios
 npm run e2e:android
 

package/index.js

@@ -0,0 +1,24 @@
+/**
+ * @format
+ *
+ * Expo entry — registerRootComponent handles both Expo Go and bare/
+ * prebuild flows. The gesture-handler import has to be the very first
+ * thing the app evaluates.
+ */
+
+import 'react-native-gesture-handler';
+// Polyfill `crypto.getRandomValues()` before anything that pulls in
+// uuid — RN's JS runtime doesn't ship one, and uuid throws
+// "crypto.getRandomValues() not supported" on the first send.
+// The library entry (src/main.ts) loads this too, but the testbed
+// here mounts the chat directly without going through that entry, so
+// we need it again at the testbed root.
+import 'react-native-get-random-values';
+// Configure LogBox before App (and its expo-av / styled-components
+// imports) evaluate, so import-time dev warnings don't flash the on-screen
+// "view warnings" toast over the chat UI. Testbed-only.
+import './setupLogBox';
+import { registerRootComponent } from 'expo';
+import App from './App';
+
+registerRootComponent(App);