[raj-dubey1]

Why

The Docs MCP server builds its implementation bundles from these pages: each bundle is a platform's integration guide plus its AI reference (llms) page. So these pages are the only source for what AI coding agents get. I followed each quickstart on the latest kit and toolchain. These fixes are what it took for an app built only from the pages to install and compile.

Page fixes, against the latest releases

iOS (UI Kit 5.2.3, chat-sdk-ios 4.1.10, calls-sdk-ios 5.0.4)

• getting-started, llms-ios-v5, calling-integration, call-features, ai-assistant-chat-history, overview, components-overview, troubleshooting:
  • Install with Swift Package Manager, Up to Next Major from 5.2.3. The kit's Package.swift pulls in CometChatSDK 4.1.10+, so nobody pins it by hand any more; an exact 4.1.9 pin fails to resolve.
  • The Calls SDK is 5.0.4 and optional.
  • Minimum iOS is 15.1.
  • CocoaPods is marked deprecated. The pages said pod 'CometChatUIKitSwift', '5.1.22', but CocoaPods trunk stops at 5.1.18.
• message-list: the type is MessageListAlignment (.standard / .leftAligned), and hideAvatar is Bool?. threaded-messages-header no longer shows .right.
• Feature pages (pinned and saved messages, thread subscription) say they need CometChatSDK 4.1.9 or later and that the package manager resolves it. They no longer read as an exact-pin step.

Android (chatuikit 6.2.0, calls-sdk-android 5.1.0)

• One version everywhere, replacing 6.0.6 / 6.0.3 / 5.0.1 / 6.+. The UI Kit doesn't bundle the Calls SDK, so calling pages add calls-sdk-android:5.1.0 next to it (from main's 6.2.0 ringing pages, docs(android): UI Kit ringing pages for v6.2.0 #607). Covers getting-started*, llms-android-v6, calling-integration, call-features, upgrading-from-v5 and message-template.
• Build fixes on the latest toolchain (AGP 9.4, Gradle 9.8, Kotlin 2.4). Each one fails the build without it:
  • CallbackListener<String> replaces <String?>.
  • Compose BOM and material3 are added.
  • compilerOptions replaces kotlinOptions, which is an error on Kotlin 2.4. JVM target 17, which the Calls SDK needs.
  • An AGP 9 note: built-in Kotlin, so don't apply kotlin.android. AGP 8 is still covered.
• The Compose 1.7 warning is reworded: a normal build gets Compose 1.8 through cards-android, and only a forced 1.7 pin crashes.

React (UI Kit 7.2.4)

• integration-react and 41 other pages: App.tsx imported CometChat only for types, which fails npm run build on Vite's default strict template (TS6133). They now use import type { User, Group, Conversation }.
• main.tsx keeps ./index.css and StrictMode.
• CRA is marked deprecated.
• The peer list includes the optional calls SDK, and the <21 ranges are escaped so the pages parse.
• Code blocks that used CometChat.X with no import now import it, as a type or as a value where instanceof or SDK calls need it.
• Removed APIs that don't exist in v7: CometChatMessages and CometChatMessageComposer.AIButton. callSettingsBuilder is a SessionSettings object.

React Native (UI Kit 5.5.2, calls-sdk-react-native 5.1.0)

• Node 22.13+, which React Native 0.88 requires.
• The base install pins @react-native-async-storage/async-storage@^2.1.2 (the range the Calls SDK declares) and react-native-svg@^15.16.0 (inside the SDK's declared ^15.12.0, and the first release whose podspec targets iOS 15.1), so adding calling later doesn't downgrade anything. @react-native-community/datetimepicker is dropped; the 5.5.2 kit doesn't use it.
• The calling dependencies match the Calls SDK 5.1.0 declared peers (react-native-webrtc@^155.0.1), including on call-features. The old list was from v4 and failed with ERESOLVE.
• iOS deployment target is 15.1 everywhere. Podfile samples no longer exclude arm64 for the simulator, which broke Apple Silicon Macs, or set bitcode.
• The stale async-storage local_repo Gradle step is gone, also from sdk/react-native/setup-sdk and llms-react-native-v4. The Chat SDK needs async-storage at runtime but doesn't declare it.
• The AI page lists the 5.5.2 peers instead of saying "verified against 5.4.0".

Angular (UI Kit 5.2.2)

• integration, quickstart, components/cometchat-message-list:
  • Angular 17–21. quickstart said 22 is supported, but the kit's peer range is <22.
  • The install includes @cometchat/cards-angular and dompurify.
  • Angular 20+ file names.
  • init()?.then.
  • A working CSS import path.
  • A production budget step.
  • Numeric alignment enums.
• Every sample that sets state in a promise, an await or a subscription uses signals. A fresh Angular 21 app is zoneless, and plain fields left it stuck on "Loading...".
• main.ts samples use init()?.then and App/app.ts (Angular 20+), with a note for 17–19.
• The CSS import path is fixed in the migration guide and troubleshooting.

mcp-server.mdx: the bundle table says which pages each bundle is built from, and adds angular-uikit-quickstart. Production (mcp.cometchat.com) and staging both serve the Angular bundle now, so this can merge without waiting on a deploy.

Merged with main

main is merged in (bed01a0). It brought the Android UI Kit 6.2.0 ringing pages (#607) and the React Native Calls 5.1 pages. Versions follow main where it was newer: Android UI Kit 6.2.0 + Calls 5.1.0, RN Calls 5.1.0 with react-native-webrtc 155.0.1 and react-native-svg ^15.16.0. This PR's own pages that main made stale were updated to match (d26ce46).

Verification

I built fresh apps from the page snippets only:

• Android: Compose and Views apps on AGP 9.4.1, plus Compose on AGP 8.13. assembleDebug passes. These builds ran on UI Kit 6.1.1, before the merge. The 6.2.0 artifacts have the same POM dependency set, the Compose kit still calls the Compose 1.8 LazyColumn overload, and the Kotlin kit still has no MessageTemplate API, but the apps weren't rebuilt on 6.2.0.
• iOS: a chat app and a calls app built with Xcode. xcodebuild succeeds for the Simulator.
• React: a Vite react-ts app. npm run build passes; it failed with TS6133 before. Login, conversation list and sending a message work.
• React Native: an RN 0.88 project. Every install command passes with no ERESOLVE; it failed before. This ran on Calls 5.0.6; the commands now use the 5.1.0 peer ranges and weren't re-run.
• Angular: an Angular 21 app built only from the Docs MCP, plus an Angular 19 app. npm install without --legacy-peer-deps passes, ng build passes with no warnings, and login, the conversation list and sending a message work. All 32 converted samples compile under strict templates.

The Docs MCP's new package-version check passes for every pin on this preview.

Notes

• CODEOWNERS on main reads - @jitvarpatil. GitHub reads - as a path, so no default reviewer is requested. This PR no longer changes that file; fix it separately if that's intended.
• The moderation Add Rule schema says isKeywordReferencePresent, but its examples use isKeywordsReferencePresent. Not changed here.
• On PR previews, Mintlify redirects /ui-kit/react/integration-* to the site root. Production is unaffected.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Efu4EKfePzK3Z6QQVp2hm4

[mintlify]

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

Project	Status	Preview	Updated
cometchat	🟢 Ready	View Preview	Nov 12, 2026, 5:50 PM

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

[ketanyekale]

Approving, with one merge-order condition. Every page here is a modify; nothing is added, removed or renamed, so there's no redirect or 404 risk. The Mintlify build and link-rot checks pass.

Merge order (must do)

• The live Docs MCP doesn't serve angular-uikit-quickstart yet. list_cometchat_bundles returns 10 bundles with no Angular one, and none was verified after 2026-04-29. As you noted, deploy the MCP server first. Otherwise mcp-server.mdx lists a bundle that agents can't fetch.

Checked against the registries (all match)

• iOS: cometchat-uikit-ios 5.2.3 is the latest release. Its Package.swift declares chat-sdk-ios from: "4.1.10" and cards-sdk-ios from: "1.2.0", so moving from an exact pin to Up to Next Major is right. calls-sdk-ios 5.0.4 is real. The old 5.1.22 shows up only in "Available since" lines, which is fine.
• Android: chatuikit-kotlin-android and chatuikit-compose-android are both 6.1.1 on Cloudsmith. The 6.1.1 POM pulls in chat-sdk-android 5.0.7 and chatuikit-core-android 6.1.1, which matches llms-android-v6. calls-sdk-android 5.0.4 is the latest. No 6.0.x, CallbackListener<String?> or kotlinOptions snippets are left.
• React: @cometchat/chat-uikit-react 7.2.4 is the latest. The import type { User, Group, Conversation } change in App.tsx is correct.
• React Native: UI Kit 5.5.2 and calls-sdk-react-native 5.0.6 are both the latest. The Calls SDK's declared peers match the pinned ranges exactly (react-native-svg ^15.12.0, async-storage ^2.1.2, react-native-webrtc ^124.0.7, react-native-performance ^5.1.2, react-native-url-polyfill ^2.0.0, react-native-background-timer ^2.4.1). Dropping datetimepicker matches the 5.5.2 peer list. Removing local_repo holds up because async-storage is now pinned to 2.x, and nothing links to the removed troubleshooting anchor.
• Angular: UI Kit 5.2.2's peers are @angular/core >=17.0.0 <22.0.0, @cometchat/cards-angular ^1.0.0, dompurify ^3.0.0 and chat-sdk-javascript ^4.2.0. The 17–21 range and the install commands match.

Docs structure

• No unresolved nav refs, so the build is safe. No broken internal links in the changed files or anywhere in scope. No pages dropped from nav. The 7 "orphans" are the hidden llms-* AI reference pages and one legacy Angular 2.0 page, all already like that on main.
• Anchors referenced from the new text exist (campaigns#step-3-add-cometchatsdk-to-the-extension, troubleshooting#cocoapods-issues).

Nits (optional)

• mcp-server.mdx: the get_cometchat_implementation_bundle card describes what will be true only once the new MCP is deployed. That's one more reason to merge after the deploy.

[jitvarpatil]

Approving — with two merge-ordering conditions

Valuable PR: these pages are the only input the Docs MCP server gives AI coding agents, so a stale version here turns straight into generated code that doesn't build. It is 118 files, so the below is a targeted check of the riskiest claims rather than a line-by-line pass — but everything I checked is right.

✅ Every pinned version is published

Kit	Pinned here	Published latest
iOS UI Kit	5.2.3	5.2.3 (public release Oct 8)
Android chatuikit	6.1.1	6.1.1 (kotlin + compose on Cloudsmith)
React UI Kit	7.2.4	7.2.4
React Native UI Kit	5.5.2	5.5.2

Several recent docs PRs pinned versions that weren't published yet; this one avoids that across the board.

✅ iOS — verified against the published 5.2.3 xcframework and Package.swift

• .iOS("15.1").
• CometChatSDK from: "4.1.10" — so "nobody pins it by hand; an exact 4.1.9 pin fails to resolve" is exactly right.
• enum MessageListAlignment { case standard, leftAligned }.
• CometChatMessageList.hideAvatar: Bool?.

✅ Peer dependencies

• Angular: kit 5.2.2 peers @angular/core >=17.0.0 <22.0.0, so the Angular 21 samples are in range.
• RN react-native-svg: the UI Kit declares "*" while the Calls SDK requires ^15.12.0 — pinning to the Calls range is the right call, since the kit's own constraint gives a reader nothing to work with.
• RN async-storage: not a declared peer, consistent with treating it as a runtime requirement rather than a dependency.

🟠 Condition 1 — #556 must merge with or before this

This PR makes 6.1.1 the install version on every Android page. In 6.1.1, CometChatNotificationFeed's callbacks changed from public var to private var + setOnX(...) setters (CometChatNotificationFeed.kt:84-87, 521-536). #556 migrates the feed.onX = { … } snippets on notification-feed.mdx and campaigns.mdx.

The two PRs share no files, so nothing will flag the gap: if this lands alone, the quickstart installs 6.1.1 while those pages show code that doesn't compile against it. #556 was waiting on 6.1.1 to publish — it now has, and I've approved it.

🟠 Condition 2 — #535 overlaps 8 iOS files and disagrees on a fact

Both edit getting-started, calling-integration, call-features, core-features, llms-ios-v5, threaded-messages-header, troubleshooting and upgrading-from-v4. Beyond the conflicts, they contradict each other on the SPM dependency, and this PR has it right: #535 still says UI Kit versions before 5.2.2 don't declare CometChatSDK and to pin 4.1.9 for 5.1.22–5.2.1, but the public 5.2.1 Package.swift already declares from: "4.1.10", so that pin fails to resolve on 5.2.1.

Suggested order: merge this first, then rebase #535 and drop its conflicting SPM paragraph — that resolves #535's remaining issue for free instead of reconciling two versions of the same section.

[jitvarpatil]

🤖 Review Buddy (review-docs-pr)

Recommendation: request changes. Automated review; the final decision stays with a maintainer.

TL;DR: This PR won't break the docs build or any links. It only modifies files, so no redirects are needed. The iOS, React, React Native and Angular changes are consistent within each platform. The problem is Android. The PR was written against UI Kit 6.1.1. Main has since moved Android to UI Kit 6.2.0 + Calls SDK 5.1.0, and the merge (bed01a0) left the pages mixing the two versions. The Android AI reference page now says two different things about the latest version. That page goes straight into the android-uikit-quickstart MCP bundle, and feeding agents correct content is the whole purpose of this PR. One P1 and three P2s.

Checked at bed01a0dfa0e834265e03956570dd6f2acdb136f (114 files, +1345 / −1088).

P0: none

P1: fix before merge

1. Android pages mix two UI Kit versions after the merge with main.
   • ui-kit/android/llms-android-v6.mdx:39: "Latest versions: UI Kit 6.1.1". Lines 21–23 of the same page say 6.2.0 and Calls 5.1.0. This AI reference page is part of the Android MCP bundle, so agents get two different answers.
   • ui-kit/android/upgrading-from-v5.mdx:62 and :75 pin chatuikit-kotlin-android:6.1.1 and chatuikit-compose-android:6.1.1. Main had 6.x.x here, so this PR adds the older pin. The same page (:389) tells readers to add calls-sdk-android:5.1.0. calling-integration.mdx:69 says that UI Kits before 6.2.0 crash at launch without the Calls artifact.
   • Fix: change both to 6.2.0 to match getting-started*.mdx and calling-integration.mdx, or use 6.x.x as main had.

P2: nits

2. Version claims still say 6.1.1 on pages that now install 6.2.0. These were verified on 6.1.1, and the PR's Android build checks also ran on 6.1.1. Either re-check them on 6.2.0 or drop the version number:
   • ui-kit/android/getting-started.mdx:167, getting-started-kotlin.mdx:128, troubleshooting.mdx:71: "UI Kit 6.1.1 builds without Jetifier"
   • ui-kit/android/getting-started-jetpack.mdx:131: the Compose 1.7 note quotes the 6.1.1 POM and the BOM from cards-android 1.0.0. This page is also in the Android MCP bundle.
   • ui-kit/android/message-template.mdx:9: "verified against the published artifact 6.1.1"
3. The page lists an MCP bundle the live server doesn't serve yet. mcp-server.mdx:127 lists angular-uikit-quickstart. The PR body says the live Docs MCP server doesn't serve it yet. Deploy the server before merging, as the author notes, or the page documents a bundle that doesn't exist.
4. React Native react-native-svg wording. ui-kit/react-native/calling-integration.mdx:12 calls ^15.16.0 the "declared range", but the other pages say the Calls SDK declares ^15.12.0 and that ^15.16.0 is the first release whose podspec targets iOS 15.1. The PR body also says the base install pins ^15.12.0, but every page installs ^15.16.0. The install commands are consistent with each other; only the wording disagrees.

Passed

• Build: 0 navigation refs that don't resolve (docs.json).
• Redirects: 0 files removed or renamed, so none needed. Redirect count is unchanged (927 → 927), and 0 chained 404s.
• Links: 0 broken internal links in the 517 ui-kit/ pages. A repo-wide scan found 21 broken targets, all in pages this PR doesn't touch, so they aren't caused by it.
• Orphans: the 16 unlinked ui-kit/ pages are the hidden llms-* AI reference pages and old kotlin/2.0 pages. None are new.
• iOS: the same versions throughout (UI Kit 5.2.3 on SPM, CometChatSDK 4.1.10+, Calls 5.0.4, iOS 15.1, CocoaPods at 5.1.18). No leftover pod '…' pins and no iOS 13/14 minimums.
• Angular: the 17–21 range, the @angular/cli@21 scaffold and the zoneless/signals guidance agree across integration, quickstart and troubleshooting.
• React: all v7 integration pages use import type. The bare CometChat.X matches the scan found are in v4/v5/v6 pages, type-signature reference blocks, or snippet fragments this PR doesn't touch.
• React Native: the Calls SDK peer ranges are the same across calling-integration, call-features, expo-integration, react-native-cli-integration, llms-react-native-v5 and sdk/react-native/setup-sdk.
• Skipped: the Mintlify preview wasn't rendered, and none of the snippets were compiled here. The PR's own build checks (Android on 6.1.1, iOS, React, React Native, Angular) were not re-run.

[jitvarpatil]

🤖 Review Buddy (review-docs-pr)

Recommendation: request changes. Automated review; the final decision stays with a maintainer.

TL;DR: This is a re-review at d26ce46. The Android and React Native problems from the last review at bed01a0 are fixed. Android now says 6.2.0 everywhere, including llms-android-v6.mdx:39 and upgrading-from-v5.mdx:62/75. The only 6.1.1 mentions left are "from v6.1.1" availability notes on pages this PR doesn't touch, and those are correct. The RN svg wording at calling-integration.mdx:12 now explains why it uses ^15.16.0. The build and links are still safe.

One new problem comes from a release that shipped after the PR was written. @cometchat/chat-uikit-angular 5.2.3 (published 2026-11-06) raised its peer floor to Angular 18. The pages still say Angular 17–21, and they install the kit unpinned. So an Angular 17 reader who follows them now gets ERESOLVE. One P1, two P2s.

Checked at d26ce4681edd96d93e30d5fcdef5b71a2fd7a6e9 (114 files, +1345 / −1088).

P0: none

P1: fix before merge

1. Angular 17 is listed as supported, but the latest kit doesn't support it. npm view @cometchat/chat-uikit-angular@5.2.3 peerDependencies returns @angular/core / @angular/common >=18.0.0 <22.0.0 and dompurify ^3.4.17. 5.2.2 returned >=17.0.0 and ^3.0.0. The install commands are unpinned (integration.mdx:63, :68, quickstart.mdx:20), so they resolve 5.2.3. The pages that need changing:
   • ui-kit/angular/integration.mdx:12, :13, :39, :73: "17–21", >=17.0.0 <22.0.0, dompurify ^3.0.0. Line 73 even says an ERESOLVE "almost always means the Angular major is outside 17–21". On 17, that advice sends the reader the wrong way.
   • ui-kit/angular/quickstart.mdx:10: "Angular 17, 18, 19, 20 or 21 — the UI Kit declares >=17.0.0 <22.0.0"
   • The Angular 17 notes in integration.mdx:144, :195, :275 and quickstart.mdx:88, plus overview.mdx ("17-21").
   • Fix: say Angular 18–21 and dompurify ^3.4.17. If you want to keep supporting 17, add a note to pin @cometchat/chat-uikit-angular@5.2.2 there. These pages feed the angular-uikit-quickstart MCP bundle, so agents will repeat the 17 claim.

P2: nits

2. Merge order: the Docs MCP deploy has to come first. mcp-server.mdx lists the angular-uikit-quickstart bundle. The live server didn't serve it at the last check, and the PR body says the same. Deploy the server before merging.
3. React Native: the svg range named in the prose doesn't match the install step. ui-kit/react-native/react-native-cli-integration.mdx:172 and ui-kit/react-native/expo-integration.mdx:146 say "react-native-svg ^15.12.0 … already installed in Step 2". Step 2 installs ^15.16.0 (:96 / :95). That is valid, since 15.16.0 satisfies ^15.12.0, but name the range Step 2 actually installs. Also, calls/react-native/overview.mdx:18-19 uses exact url-polyfill@2.0.0 / webrtc@155.0.1, while the UI Kit pages use ^2.0.0 / ^155.0.1. Pick one form.

Passed

• Build is safe: 0 unresolved nav refs. 0 removed or renamed files, so no redirects are needed (redirect delta +0) and there are no chained 404s.
• In-content links: there are 24 broken occurrences across the repo, but none of them is in a file this PR changes. All are already on main.
• Versions against the registries today:
  • iOS: 5.2.4 is now the latest. Its Package.swift still has .iOS("15.1") and CometChatSDK from: "4.1.10", so "Up to Next Major from 5.2.3" resolves correctly.
  • React: 7.2.6 has the same peers as 7.2.4, so ^7.2.4 is fine.
  • React Native: UI Kit 5.5.4 has the same peers as 5.5.2. Calls SDK 5.1.0 peers (webrtc ^155.0.1, svg ^15.12.0, async-storage ^2.1.2, performance ^5.1.2, url-polyfill ^2.0.0, background-timer ^2.4.1) match the pages.
• Fixes from the last review: llms-android-v6.mdx:39 says 6.2.0, upgrading-from-v5.mdx:62,75 pin 6.2.0, and the Jetifier, Compose 1.7 and MessageTemplate notes name 6.2.0. The RN svg rationale is explained at ui-kit/react-native/calling-integration.mdx:12.
• Not re-run here: the author's fresh-app builds (Xcode, AGP, Vite, RN, ng build). This review checks the content against the registries only.

[jitvarpatil]

✅ Approved via Review Buddy after an automated review (P0: 0 · P1: 1 · P2: 2).

Findings: #568 (review)