@ethora/chat-component-rn 26.7.6 → 26.7.8

package/CHANGELOG.md

@@ -7,6 +7,9 @@ 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.
+
+- **`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.
 
 - **Profile header polish (both the chat and the user profile).** The back / "…" row is taller and sits further from the top edge, and its buttons are inset 20 pt so a button's centre line matches the collapsed avatar's — they used to sit closer to the edge than the avatar below them. The glyphs inside the hero's round buttons always paint white now (several SDK icons ignore their `color` prop and paint white regardless, so tinting the rest to the title colour left a mix of black and white in one row); on a light fill the circle darkens instead of the glyph. And on the user profile the "…" menu appears once the header is collapsed, carrying exactly the same actions the hero's buttons do — collapsed, those buttons are off-screen and were unreachable.
@@ -57,6 +60,8 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this pr
 ### Fixed
 
 - **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`.
 - **`allRoomPresences` reported a failure on every bootstrap.** `presenceInRoom` schedules its resolve `delay` ms (2000) after the room's reply and races a 2000 ms timeout that rejected with `undefined` — the timeout won, so a join that had succeeded was logged as `allRoomPresences failed`. The timeout no longer rejects once the reply has been seen.
 
 - **The signed-in user's description was thrown away on every login.** `unpackAndTransform` (the shaper `setUser` runs every payload through) hardcoded `description: ''`, so the profile's About section could never show your own bio no matter what the server returned. It now carries `input?.description` through.