Navigation — embedding the chat

ChatNavigator registers every chat screen and mounts CallProvider (incoming-call overlay, call signaling). List taps open the room, info, etc. without host route wiring.

Screens in the chat stack (AppScreen.*):

ChatRoomParams: conversationId, receiverUser, isGroup, groupName, peerDisplayName, openSearch, initialSearchQuery, focusMessageId, threadRootId.

1// src/navigation/BottomTabs.tsx2<Tab.Screen name="Chat">3  {() => (4    <ChatProvider config={chatConfig}>5      <ChatNavigator withContainer={false} />6    </ChatProvider>7  )}8</Tab.Screen>

With withContainer={false} the chat stack registers itself with the call and push routers, so incoming-call accept and notification taps still open the right screen.

If the chat tab mounts lazily but you want the socket (presence, incoming calls) alive from app start, mount a ChatProvider + CallProvider near the root, pass your container ref, and register ActiveCallScreen in that root stack. Fieldr's version is ChatSessionHost.tsx. Minimal form:

1// src/navigation/RootNavigator.tsx2import {ActiveCallScreen, CallProvider, ChatProvider} from '@realtimexsco/live-chat-react-native';3 4<NavigationContainer ref={navigationRef}>5  <Stack.Navigator>6    {/* …your screens… */}7    <Stack.Screen name="ActiveCallScreen" component={ActiveCallScreen} options={{gestureEnabled: false}} />8  </Stack.Navigator>9  <ChatProvider config={chatConfig} withSafeArea={false} withGestureRoot={false} withToast={false}>10    <CallProvider navigationRef={navigationRef}>{null}</CallProvider>11  </ChatProvider>12</NavigationContainer>

Mount one CallProvider at a time — render the root one only while no ChatNavigator is mounted.

Post-login navigation.reset(...) calls must keep an open ActiveCallScreen route: a call answered from a killed app is often in progress before your app has finished signing in (CallProvider reopens the screen if a reset drops it).

Register the exported screens (ConversationListScreen, ChatRoomScreen, ChatInfoScreen, CreateGroupScreen, SelectUserScreen, SelectGroupMembersScreen, GlobalMessageSearchScreen, NotificationSettingsScreen, MentionsScreen, CanvasListScreen, CanvasEditorScreen, CallsHistoryScreen, ActiveCallScreen) under the AppScreen.* names — screens navigate to each other by those names — and mount CallProvider with your navigationRef. Param types: ChatStackParamList, ChatRoomParams, ChatInfoParams, CreateGroupParams, SelectGroupMembersParams, CanvasListParams, CanvasEditorParams, CallsHistoryParams. CallRecordingsScreen is not exported from the package root, so the room menu's Recordings entry only works inside ChatNavigator — hide it with roomOptions: {recordings: false} otherwise.