@robono/messaging-react-native 0.7.0 → 0.9.0

package/CHANGELOG.md

@@ -1,4 +1,12 @@
-## 0.7.0 — unreleased
+## 0.9.0 — release candidate
+
+Supply hosted connections, durable offline actions, interface language, localized Maps/calls, and retryable native upload errors. Use native calling 0.7 and Maps 0.3 with an app rebuild.
+
+## 0.8.0
+
+Connect the supplied Expo Messenger to native incoming calls automatically. Register VoIP/system calling with the existing signed-in device, clear account state on sign-out, cache contact names and use selected Android calling appearance. Requires calling-react-native 0.6.0 and a native app rebuild.
+
+## 0.7.0 — 2026-11-04
 
 Supply automatic Expo calling, Maps and connected chat extras. Use Messenger attachment menus, grouped media, bounded dialogs and anchored inbox actions. Connect managed call alerts, unanswered-call messages and call-aware media audio. Stop location and pending uploads during account cleanup.
 

package/README.md

@@ -1,11 +1,48 @@
 # Optional Robono messaging screens
 
+## Recommended hosted installation
+
+Run `npx --package @robono/server robono-messenger-install` in your Expo project. The installer sets up the connection and native plugin. Robono runs the communication services; your server verifies the existing login and issues its short-lived session. See the server package's [hosted guide](https://robono.com/guides/hosted-messenger.html).
+
+```tsx
+import {createHostedExpoMessenger, ExpoMessenger} from '@robono/messaging-react-native/expo';
+import {hostedRobonoTokenProvider} from '@robono/messaging';
+const messenger = await createHostedExpoMessenger({
+  userId: session.userId,
+  tokenProvider: hostedRobonoTokenProvider({
+    tokenEndpoint: 'https://your-app.example/api/robono-token',
+    getAccessToken: () => session.accessToken(),
+  }),
+});
+<ExpoMessenger {...messenger} userId={session.userId}
+  companyName="Your company" contacts={contacts} />
+try { await messenger.signOut(); } finally { await session.signOut(); }
+```
+
+Create this connection outside repeated renders, and dispose it when unmounting. Use the generated component to handle account changes and retries automatically. The lower-level `createExpoMessenger` and server forwarding adapters remain available for an optional self-hosted connection.
+
+Install the native dependencies below and rebuild both platforms. For alerts
+outside the app, `createExpoMessenger` connects the managed service automatically. Use the Account screen’s Enable notifications action and follow
+`@robono/server/NOTIFICATIONS.md`: iPhone needs **your** Apple Team ID, APNs Key ID,
+private .p8 key and Bundle ID; Android needs **your** Firebase project, app
+configuration and a service-account key uploaded in Robono’s private notification setup. Never ship private keys in the
+app. Website chat itself does not require these mobile credentials.
+
+The supplied group owner, shared-media, reply and pinned-message screens use the
+same popup boundaries as Messenger. Global search and group controls require the
+matching server and service migrations. Imported groups need a server-assigned
+owner before users can edit them. Optional offline received history is disabled
+by default; its network-selected expiry is honored and it is read-only offline.
+Revocation while disconnected is not known until reconnection or expiry. Logout
+clears the local account's history. `persistence:false` disables these local stores.
+
+
 Use a ready-made direct or group conversation screen, replace its sections, or compose the exported components into your own layout. Use `ExpoMessenger` for the complete inbox and conversation flow, or the individual components inside your existing navigation. The complete Expo messenger connects notification registration; nothing requests permission on mount. The shared icon controls require `react-native-svg` (install it with your framework’s native dependency installer).
 
 ## Connected features
 
 The complete messenger connects selected calling, chat weather/tracking and Maps
-through the same authenticated server route. Customers do not supply fake demo
+through Robono’s authenticated hosted connection. Customers do not supply fake demo
 callbacks or create separate call controllers for this setup. Feature selection
 and appearance remain in **Features & preview**. Advanced custom interfaces can
 still use individual components and callbacks.
@@ -26,7 +63,7 @@ own database; retries with the same values are safe. Keep group membership in th
 messaging group API; eligible groups use that same membership for calls. Supergroups
 never start calls, and voice/video calls remain limited to eight people.
 
-The host's `authorize` function checks `calling.*`, `extras.*` and `location.*` as
+For the optional self-hosted connection, the host's `authorize` function checks `calling.*`, `extras.*` and `location.*` as
 well as messaging operations. Account checks have no conversation ID; call actions
 use the actual conversation from the service, never a caller-supplied claim. Keep
 current membership, suspension and feature restrictions in those checks.
@@ -44,40 +81,6 @@ capture and calls, cancels unfinished tracking and unregisters the device. Old
 account credentials and unfinished work must never be reused for another person.
 
 
-## Recommended installation
-
-Connect `createRobonoMessengerServer` from `@robono/server` at one authenticated
-HTTPS route. It supplies managed private attachments. Create one connection per
-signed-in account, outside repeated renders:
-
-```tsx
-import {createExpoMessenger, ExpoMessenger} from '@robono/messaging-react-native/expo';
-const messenger = createExpoMessenger({
-  endpoint: 'https://your-app.example/api/robono',
-  userId: session.userId,
-  getAccessToken: () => session.accessToken(),
-  isCallActive: () => calls.isActive(),
-});
-<ExpoMessenger {...messenger} userId={session.userId}
-  companyName="Your company" contacts={contacts} />
-// On logout, before destroying the user's session:
-try { await messenger.signOut(); } finally { await session.signOut(); }
-```
-
-Install the native dependencies below and rebuild both platforms. For alerts
-outside the app, `createExpoMessenger` connects the managed service automatically. Use the Account screen’s Enable notifications action and follow
-`@robono/server/NOTIFICATIONS.md`: iPhone needs **your** Apple Team ID, APNs Key ID,
-private .p8 key and Bundle ID; Android needs **your** Firebase project, app
-configuration and a service-account key uploaded in Robono’s private notification setup. Never ship private keys in the
-app. Website chat itself does not require these mobile credentials.
-
-The supplied group owner, shared-media, reply and pinned-message screens use the
-same popup boundaries as Messenger. Global search and group controls require the
-matching server and service migrations. Imported groups need a server-assigned
-owner before users can edit them. Optional offline received history is disabled
-by default; its network-selected expiry is honored and it is read-only offline.
-Revocation while disconnected is not known until reconnection or expiry. Logout
-clears the local account's history. `persistence:false` disables these local stores.
 
 ## Individual screen inside existing navigation
 
@@ -252,7 +255,7 @@ Blocking retains history and stops direct messages and calls for that pair in yo
 
 Enable Reactions to show an emoji ribbon beside the long-pressed bubble, or the hover smile icon on desktop. Selected reactions stay above the delivery indicator. Polls are interactive chat messages created from the attachment menu. Transcript is a separate voice-message action. In the header's three-dot menu, choose translation **Off / Text / Voice** and languages once for the conversation. The saved choice controls Translate or Play Translation on eligible incoming messages; own messages and matching sender/target languages do not show it. The result has Show original / Show translation controls. Expo supplies translated-voice playback and its audio session; an explicit Play Translation action starts playback when ready. `language` supplies the initial target and `contact.language` / `participants[id].language` supply known sender languages, with a saved conversation incoming-language fallback. Defaults to Off. The Expo private outbox retains preferences across restarts on this device. Custom contact menus can call `client.setTranslationPreference({mode:'text',language:'es',sourceLanguage:'en'})`. Connect `MessagingClient.transformRequest` to the authenticated `createMessagingTransformBackendAdapter` on your server.
 
-### November 1 behavior update (unpublished)
+### November 1 behavior update
 
 The default palette follows Messenger. Existing saved customer colors remain in
 place. Direct chats use the brand header; groups use Messenger’s blue header.