fix(ui-kit/react-native): unexported imports, wrong event names, the missing unban path and Ongoing Call page — ENG-39154

[suraj-chauhan-cometchat]

Description

Four changes to the React Native UI Kit docs from the ENG-39154 triage, one commit each. Every claim below was checked against the kit and SDK source, and every changed code block was compiled.

1. Four pages imported names the kit does not export — ENG-39166 (59bac322)

Copied into a TypeScript project, each of these imports failed with TS2305 (no exported member).

Page	Before	After
call-buttons	new OutgoingCallConfiguration({...})	a plain object passed to outgoingCallConfiguration
compact-message-composer	EnterKeyBehavior.SendMessage	CometChatUiKitConstants.EnterKeyBehavior.SendMessage, which is already public
compact-message-composer	a "Configuration" section built from SingleLineMessageComposerConfiguration	removed: it is not exported and no component takes it. Every option it showed is already a documented composer prop (hideVoiceRecording under its main name, hideVoiceRecordingButton)
component-styling	a standalone <CometChatReceipt>	the theme override applied to CometChatConversations
search	import { SearchStyle }	the type derived from CometChatSearch

The receipts example does not use CometChatMessageList on purpose. Message bubbles pass their own receipt style, which wins the merge. Run against the kit's default theme and its real merge, a read receipt resolves to the override (#FFAB00) in Conversations but stays at the bubble default (#09C26F) in the message list.

2. The events page listed names the kit never emits — ENG-39167 (a0aae25a)

A listener copied from the page silently never fired.

• ccUserUnblocked → ccUserUnBlocked, and ccGroupMemberUnbanned → ccGroupMemberUnBanned.
• ccLiveReaction removed; the kit has no such event.
• The call table listed six on… callbacks (onIncomingCallAccepted, onCallInitiated, …) that are not UI Kit event names. It now lists the four call events the kit emits: ccCallAccepted, ccCallRejected, ccCallEnded, ccOutgoingCall. The kit also declares ccCallInitiated, ccOutgoingCallAccepted and ccOutgoingCallRejected as listener keys, but nothing emits them, so outgoing accept/reject now points to the Chat SDK's call listener.
• Call handlers receive { call }. ccCallRejected also fires when the user cancels their own outgoing call, and one ccCallEnded path sends no call.
• ccActiveChatChanged moved to message events: it is emitted with emitMessageEvent, so only addMessageListener receives it.
• The CometChatUIEventListener heading named a symbol the kit does not have; it is now "UI Events".

3. No documented way to undo a ban — ENG-39170 (aaa21c0f)

CometChatGroupMembers gives owners, admins and moderators a Ban option by default, but the UI Kit has no screen to list banned members or unban them, and guide-group-chat never said so. The Chat SDK page group-kick-ban-members already documents both, and the guide now points to it:

• Section 4 now says what the members menu offers and to whom.
• A note after the section 4 example links to listing banned members, unbanning, and hideBanMemberOption.
• The feature matrix gains "Unban member" and "List banned members".

4. The in-call screen had no page — ENG-39171 (af864950)

The kit exports CometChatOngoingCall, the screen users see during a call, but the React Native v5 docs never had a page for it. Only the v4 page exists, and /ui-kit/react-native/ongoing-call redirects to the docs home. iOS and Vue have current Ongoing Call pages, so the new page follows the iOS structure (Usage, Customization, Common Patterns); Vue's is an older props-only page. It uses React Native code and documents only what the RN kit supports:

• Props: only sessionID, callSettingsBuilder and onError. There is no style prop and there are no view slots, and the component emits no UI events of its own.
• Integration: render it with a session ID and a CallSettingsBuilder whose OngoingCallListener ends the session, the same steps CometChatIncomingCall takes. Incoming and Outgoing Call normally render it for you.
• Filters: a table of CallSettingsBuilder methods and their defaults, taken from the Calls SDK typings. The three methods the SDK marks obsolete are left out.
• Events: only Incoming and Outgoing Call emit ccCallEnded, so it never fires for a call screen you render yourself.
• Your own builder on Incoming Call, Outgoing Call or Call Buttons: these components set their own OngoingCallListener on it, and they skip their default layout and audio-only settings.

The page is also added to the nav after Outgoing Call, as on iOS, and to the Calling catalog in components-overview.

Related Issue(s)

• Parent: ENG-39154
• Addressed here: ENG-39166, ENG-39167, ENG-39171, and item 1 of ENG-39170 (the ban round trip). Items 2 and 3 of ENG-39170 stay open as follow-ups.
• Related kit bug, not part of this PR: ENG-39300. A handler passed by name, like { ccCallAccepted: handleAccept }, never fires even with the right event name, because the kit dispatches by comparing the event name with the function's .name.
• Kit bug found while writing the Ongoing Call page, not part of this PR and not yet filed: an onError function that changes between renders, such as an inline arrow, makes CometChatOngoingCall request a new call token and fall back to the loading spinner (reproduced in Jest). The page's onError example uses useCallback.

Type of Change

• Documentation correction/update
• New documentation
• Improvement to existing documentation
• Typo fix
• Other (please specify)

Checklist

• I have read the CONTRIBUTING document
• My branch name follows the naming convention
• My changes follow the documentation style guide
• I have checked for spelling and grammar errors
• All links in my changes are valid and working
• My changes are accurately described in this pull request

Additional Information

How it was verified. Compile checks used TypeScript 6.0.3 in strict mode against UI Kit 5.4.0, Chat SDK 4.0.28 and Calls SDK 5.0.5. A control file with a deliberate type error was included to prove the checker ran.

• Changed code blocks (sections 1–3): all five compile. Fragments got only the declarations they reference (user, chatUser, loggedIn). The receipts block was wrapped in a function because it starts at return, and the two alternative composer usages were compiled as separate statements.
• Misspelling checks (sections 1–3): for each of the four UI Kit blocks, a copy with one misspelled key or member fails to compile, so those blocks really are type-checked. The SDK snippet is different: CometChat.CallListener's constructor takes ...args: any[], so a misspelled handler still compiles. Its two handler names were checked against the CallListener class in the SDK's CometChat.d.ts instead.
• Old imports: all five fail with TS2305.
• Unban APIs: CometChat.BannedMembersRequestBuilder and CometChat.unbanGroupMember(), which the guide now names, compile.
• Events:
  • All 39 names on the page are accepted by their listener types.
  • The old names ccUserUnblocked, ccGroupMemberUnbanned, ccLiveReaction, onIncomingCallAccepted and onCallInitiated are rejected, and so is ccActiveChatChanged on the UI listener.
  • Each of the 39 has at least one emit site in the kit source.
  • All 39 reached a listener through the real CometChatUIEventHandler in Jest.
• Links (sections 1–3): the four links in the added lines resolve in a local Mintlify preview, and their target headings exist. Each page was also checked in that preview before commit.
• Ongoing Call page (section 4):
  • The component's source is identical in kit 5.4.0 and 5.5.0, and so are the builder props on Incoming Call, Outgoing Call and Call Buttons.
  • All 8 code blocks compile, and a misspelled copy of each fails.
  • The page's runtime claims ran in Jest against the real component, with the SDKs mocked: the spinner until the token arrives, the full-size root view, the onError codes, only the first render's settings being used, a plain settings object throwing, and the spinner color.
  • All 28 links and anchors resolve in the local preview, and the page was checked there before commit.
  • Not verified: the end-of-call steps in a live call on a device.
• Spelling and grammar: proofread by hand; the repo has no spell-check workflow.

Unrelated, not touched:

• The local preview reports an MDX parse error at sdk/react-native/authentication-overview.mdx:16:104, in a file this PR does not change. The | inside Promise<CometChat.User | null> splits that table cell, leaving <CometChat.User outside its code span, where MDX parses it as JSX.
• Eight React Native pages link to components-overview#components, an anchor that page does not have.
• The Calling catalog in components-overview lists onClosePress for CometChatOutgoingCall. Kit 5.5.0 has no such prop; the prop is onEndCallButtonPressed.

Screenshots (if applicable)

Text, table and new-page changes only; each page was verified by rendering it locally.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
cometchat	🟢 Ready	View Preview	Sep 16, 2026, 1:17 PM

💡 Tip: Enable Automations to automatically generate PRs for you.