@ethora/chat-component-rn 26.7.8 → 26.7.10

package/CHANGELOG.md

@@ -7,8 +7,7 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this pr
 
 ### Added
 
-- **Mute / unmute a chat from its profile.** A bell button joins Search, Leave and Report in the chat-profile hero (first in the row, per the design): "Unmuted" with a bell, "Muted" with a crossed bell. It toggles the caller's own membership flag through `PUT` / `DELETE /v1/chats/my/{chatName}/mute` and reads the initial state from `muted` in `/chats/my` (new `IRoom.muted`). The flip is optimistic and rolls back with an error toast if the request fails. This is a stored preference only — the server does not change push delivery by itself yet.
-
+- **`config.inputDockPaddingBottom`** - controls the input dock's bottom padding directly, used verbatim on both platforms when a number is given (0 allowed), instead of the built-in default (iOS safe-area inset, 12dp on Android). Customer-reported #44.
 - **`handlePushPayload(data)` / `openRoomFromPush(jid)` are exported from the package root.** The host owns the native push side (token, permission, tap listeners) and hands the tapped notification's `data` to `handlePushPayload`: a call push rings, a message push (`data.jid` / `chatJid` / `roomJid`) opens its room — immediately when the room list is loaded, otherwise as soon as it is (`usePendingNotification` is now mounted in `ChatWrapper` and actually opens the room; it used to find it and do nothing). The pending jid is also persisted (with a 5-minute TTL), so a tap handled by a JS context that gets replaced right after (cold-start races) still opens the room on the next mount.
 - **`config.headerLayout.safeAreaTop`** — the room-list and chat header cards pad their top by the safe-area inset and run under the status bar as one white surface. Hosts used to wrap `<Chat>` in a top-edge `SafeAreaView`, which painted its own white band above the card; on Android the card's elevation drew a hairline seam where the two met. Off by default, so existing hosts keep their layout; when on, drop the host-side top inset.
 
@@ -59,6 +58,7 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this pr
 
 ### Fixed
 
+- **Leaving a room while scrolled up marked genuinely-unread messages as read, locally and on the server (customer #42, a regression of #33 reintroduced by #38).** #38 anchored the read marker to the newest server-acknowledged message instead of `Date.now()`, but every "leaving this room" path (unmount, AppState background, the host's `isVisible` prop going false, the live `advance()` effect, `useChatRoomFocus`) then stamped that newest message unconditionally, regardless of how far the user had actually scrolled - and because the private-store merge is forward-only, a later correct (smaller) marker could never overwrite the wrong one. A per-room read boundary (`rooms.readBoundaries`, populated by `MessageList` the moment the user scrolls away from the bottom) is now the single source every one of those paths consults via the new `getReadMarkerTimestamp` helper, and is carried through to the server write as `visibleRoomTs`. Also fixed: the "New messages" divider landed one message too high (above the last read message instead of directly below it). The divider was positioned by comparing `msg.date` strings against `new Date(marker).toString()`, and `Date.prototype.toString()` has second precision - the marker was silently truncated down to the whole second, so the very message it points at compared as "newer" and fell on the unread side, disagreeing by one with the unread count (which compares exact milliseconds). `insertMessageWithDelimiter` now compares numerically, on the same server id-encoded `msgSortableMs` source the unread count itself uses, and also accepts a raw numeric marker (`new Date("1700000000000")` is an Invalid Date, so a numeric-string marker used to make every comparison false).
 - **Push notifications never arrived for users who only ever signed in through this SDK.** The `initBeforeLoad` bootstrap in `XmppProvider` re-joined rooms with presence but never sent the MucSub (`urn:xmpp:mucsub:0`) subscription — only the legacy `ChatWrapper` path did, via `initRoomsPresence`. ejabberd decides whom to push for offline messages by MucSub subscriptions, so such users had a registered device token and still got nothing ("no MucSub subscription" server-side). The bootstrap and the reconnect `onOnline` handler now subscribe every room in the store after the presence pass, regardless of how that pass ended; `pushSubscriptionService` still dedupes rooms already subscribed on the device.
 - **MucSub subscriptions are sent in parallel batches and carry unique IQ ids.** The pass used to be strictly sequential (await + 100 ms pause per room, 5 s timeout each), so a user with a few dozen rooms needed minutes and a backgrounded socket died long before the end, leaving most rooms unsubscribed. Ids were `newSubscription:<Date.now()>`, which in a batch made every request resolve on the first reply. A refused subscription now logs the server's condition (`registration-required`, `forbidden`, …) so room-config / affiliation problems are visible instead of silent.
 - **The XMPP stream is closed as soon as the app goes to the background** (`XmppClient.suspend()`), and reopened on foreground (`resume()` → immediate reconnect). Android keeps a backgrounded WebSocket alive for minutes; while it lived, ejabberd still saw the user online and routed new messages into the socket instead of sending a push — so only the very first push after a cold start ever arrived, and nothing after the app had been opened and backgrounded again. The suspend is immediate, not deferred: RN pauses JS timers while an Android app is backgrounded. A reconnect that was in flight when the app got backgrounded closes its fresh socket at once, and `resume()` skips the 3 s `stop()` timeout on the already-closed client. Opt out with `xmppSettings.keepAliveInBackground: true`.
@@ -80,6 +80,7 @@ The repo itself now lives on **Expo SDK 57 (RN 0.86.2, React 19.2.8, New Archite
 
 ### Changed
 
+- **The input dock's bottom padding now defaults to `0` when `disableKeyboardAvoidingView` is set** (it used to be the iOS safe-area inset / 12dp on Android regardless). A host that owns keyboard layout typically already places the chat above its own chrome, e.g. a tab bar, and the built-in padding added a visible extra gap there (customer-reported #44). **Behaviour change for existing consumers of `disableKeyboardAvoidingView`:** if your chat does sit at the very bottom of the screen and you want the old inset back, set `config.inputDockPaddingBottom` explicitly. Hosts that do not set `disableKeyboardAvoidingView` are unaffected.
 - **Dev/test toolchain moved SDK 54 → 57**: `expo ~57`, `react-native 0.86.2`, `react 19.2.8`, `jest-expo ~57`, all `expo-*` dev pins to `57.x`, `reanimated ~4.5`, `worklets ~0.10`, `gesture-handler ~2.32`, `screens ~4.26`, `safe-area-context ~5.7`, `svg 15.15.4`, `netinfo 12`. LiveKit dev pins moved to the RN 0.86 line: `@livekit/react-native 2.12.0`, `@livekit/react-native-webrtc 144.1.2`, `livekit-client 2.21.0`.
 - **iOS `deploymentTarget` 15.1 → 16.4** in `app.json` — the minimum `expo-modules-core@57` accepts.
 - **`StyleSheet.absoluteFillObject` → `StyleSheet.absoluteFill`** across 9 files: RN 0.86 removed `absoluteFillObject` entirely; `absoluteFill` is the same plain object on every RN version our peer range spans, so spreads keep working for SDK 54 consumers.

package/README.md

@@ -18,6 +18,7 @@ React Native chat UI + chat core for iOS and Android, powered by the Ethora plat
 - [Unread tracking in tab-based hosts](#unread-tracking-in-tab-based-hosts)
 - [Logging out](#logging-out)
 - [Customization flags worth knowing](#customization-flags-worth-knowing)
+- [Keyboard handling](#keyboard-handling)
 - [Header height & font sizing](#header-height--font-sizing)
 - [Quality & test coverage](#quality--test-coverage)
 - [Local development](#local-development)
@@ -314,6 +315,15 @@ Why awaitable: the persistence layer debounces writes by 200 ms, and the chat sl
 | `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. |
 
+## Keyboard handling
+
+| Flag | What it does |
+| --- | --- |
+| `disableKeyboardAvoidingView` | Opts out of the built-in `KeyboardAvoidingView`, so a host app that already wraps `<Chat>` in its own keyboard handling doesn't get a second one avoiding the keyboard on top of it. |
+| `keyboardStickyInput` | Wraps only the input dock in a `KeyboardStickyView` instead of avoiding the keyboard for the whole chat tree, so the message list never resizes. Ignored when `disableKeyboardAvoidingView` is set. |
+| `keyboardVerticalOffset` | Pass-through offset added on top of the iOS safe-area inset when avoiding the keyboard. |
+| `inputDockPaddingBottom` | Bottom padding on the input dock (the composer's outer wrapper). When a number is given (0 allowed), it is used verbatim on both platforms. Left unset, it defaults to `0` when `disableKeyboardAvoidingView` is set, since the host then owns layout and the chat is typically already placed above the host's own chrome (e.g. a tab bar) - the built-in padding would otherwise add an extra gap. Otherwise it is unchanged: the iOS safe-area inset, or a fixed 12dp gap on Android. |
+
 ## Header height & font sizing
 
 ### Header height (`headerLayout.height`)