Updated Integration Guide by raj-cometchat · Pull Request #440 · cometchat/docs

raj-cometchat · 2026-07-27T05:32:44Z

Description

Related Issue(s)

Type of Change

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

Screenshots (if applicable)

mintlify · 2026-07-27T05:37:09Z

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

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Jul 27, 2026, 5:37 AM

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

mintlify · 2026-07-27T05:46:53Z

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

Project	Status	Preview	Updated (UTC)
cometchat	🟡 Building	–	Jul 27, 2026, 5:32 AM

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

Replace the copy-the-UI-Kit-sample approach with the released com.cometchat:push-notifications-android:1.0.0 drop-in SDK, mirroring the new Flutter guide's structure. Covers dependency setup, Application init via PNConfiguration.Builder, forwarding FCM payloads to handlePushNotification, token registration/refresh, notification-tap and call-event listeners, badge count, testing, and troubleshooting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…s-sdk Rewrite Android push guide for drop-in push-notifications-android SDK

Consolidates the two legacy iOS pages (APNs + FCM copy-files patterns) into a single notifications/ios-push-notifications.mdx that documents the CometChatPushNotifications drop-in SDK: SPM/CocoaPods install, AppDelegate + SceneDelegate wiring, CometChatPushNotificationsDelegate for taps and calls, foreground suppression, badge, and troubleshooting. Updates docs.json nav + redirects, the notifications and getting-started landing pages (single "iOS" card, no FCM-iOS Firebase tab), and stray cross-references from Flutter VoIP and legacy iOS extensions pages.

The legacy 2.0 extensions page is out of scope for the push SDK rewrite; the redirect on the old slug handles the old link.

jitvarpatil · 2026-08-10T06:05:52Z

Docs review — 🟠 Request changes

A large push-notifications restructure (18 files, +1,104/−2,831) consolidating the split Flutter (android+ios) and iOS (APNs+FCM) push pages into single flutter-push-notifications / ios-push-notifications pages. Content and redirect intent are good — but there's an execution bug that will leave blank pages and silently defeat the redirects.

🟠 P1 — 3 old pages emptied instead of deleted (breaks their own redirects)

git diff --name-status shows these as M (modified to 0 bytes), still tracked (empty blob e69de29b), not deleted:

notifications/flutter-push-notifications-android.mdx → 0 bytes
notifications/flutter-push-notifications-ios.mdx → 0 bytes
notifications/ios-apns-push-notifications.mdx → 0 bytes

Only ios-fcm-push-notifications.mdx was correctly git rm'd.

Why it matters: the PR does add redirects for all four old URLs (e.g. /notifications/flutter-push-notifications-android → /notifications/flutter-push-notifications) — which is exactly right — but a redirect only fires when no page exists at that path. Since these 3 files still exist (empty), Mintlify serves a blank page instead of applying the redirect. So the consolidation half-works: ios-fcm redirects correctly (properly deleted); the other 3 render blank and their redirects are dead-on-arrival.

Fix: actually delete them —

git rm notifications/flutter-push-notifications-android.mdx \
       notifications/flutter-push-notifications-ios.mdx \
       notifications/ios-apns-push-notifications.mdx

— then the already-present redirects take effect.

🟠 P1 — in-content link to a deleted page

notifications/push-overview.mdx still links to /notifications/ios-fcm-push-notifications (now deleted). A redirect exists so it won't hard-404, but an in-content link shouldn't rely on a redirect — point it directly at /notifications/ios-push-notifications.

✅ What passed

Redirects added for all four consolidated old URLs + push-integration → push-overview, with correct destinations. Good coverage — just undermined by the empty files above.
Merged content is clean: both new pages have proper frontmatter (title: "Flutter" / "iOS"), a single consistent version pin (cometchat_push_notifications: ^1.0.1 — no version drift), no placeholders/TODOs, and no broken "see above/below" cross-refs from the merge.
Build/nav: 0 unresolved nav refs. (The /notifications/overview orphan the analyzer flagged is pre-existing — not in this PR.)

Well-intentioned consolidation with correct redirects and clean merged content — it just needs the 3 pages deleted rather than emptied, plus the one in-content link updated. Happy to re-check once that's done.

_{🤖 Automated docs review (Mintlify link/redirect/nav/content checks).}

Both 'iOS - FCM' and 'iOS - APNs' sample cards pointed at .../SampleAppPushNotificationAPNs/Push Notification + VoIP, which 404s (that subfolder no longer exists in the v5 branch). Collapse to a single 'iOS' card pointing at the SampleAppPushNotificationAPNs folder itself, which is where the sample now lives.

The 'resolved conflicts' merge on this branch resurrected notifications/ios-apns-push-notifications.mdx as an empty file and reintroduced the split 'iOS (APNs)' / 'iOS (FCM)' cards on notifications/push-overview.mdx pointing at deleted slugs. A blank file at the old path silently defeats the redirect, so: - git rm the empty ios-apns page so the redirect fires again. - Collapse the two iOS cards on push-overview into a single 'iOS' card pointing at /notifications/ios-push-notifications.

Same merge-conflict-resolution regression as the iOS side: the 'resolved conflicts' merge on this branch resurrected notifications/flutter-push-notifications-android.mdx and notifications/flutter-push-notifications-ios.mdx as empty (0-byte) files, which silently defeats their /notifications/flutter-push- notifications redirects, and reintroduced the split 'Flutter (Android)' / 'Flutter (iOS)' cards on push-overview pointing at the deleted slugs. Also the two Flutter sample-app cards on the notifications landing page pointed at the same sample_app_push_notifications URL. - git rm both empty Flutter pages so the redirects fire again. - Collapse the two Flutter cards on push-overview into a single 'Flutter' card pointing at /notifications/flutter-push-notifications. - Collapse the two Flutter sample-app cards on notifications.mdx into one 'Flutter' card at the same working URL.

jitvarpatil · 2026-08-10T10:37:50Z

Re-review — ✅ Approve

Both P1 findings from my earlier review are fully resolved (the new commits — "Re-delete empty Flutter push pages…", "Re-delete ios-apns page and fix stale iOS links…" — address them directly). Re-verified on head 0df4bdd.

✅ Fixed

All 4 old pages now properly deleted — analyzer reports removed: 4 (was removed: 1 with 3 emptied to 0 bytes). No 0-byte .mdx files remain in notifications/.
All 4 deleted URLs have working redirects ([2a] 0 of 4 unredirected) — and now that the files are genuinely gone, the redirects will actually fire:
- flutter-push-notifications-android / -ios → flutter-push-notifications
- ios-apns-push-notifications / ios-fcm-push-notifications → ios-push-notifications
Broken in-content link fixed — [4] 0 broken links (was 1); push-overview.mdx now links directly to /notifications/ios-push-notifications.
0 nav breaks. (The /notifications/overview orphan is pre-existing — not this PR.)

Combined with the already-verified merged content (proper frontmatter, single consistent version pin cometchat_push_notifications: ^1.0.1, no placeholders/contradictions), the consolidation is now correct end-to-end.

Nicely done on the redirect coverage. Ready to merge. 🚀

_{🤖 Automated docs review — re-check after fixes.}

jitvarpatil

Re-review — ✅ Approve

Both P1 findings from my earlier review are fully resolved (the new commits — "Re-delete empty Flutter push pages…", "Re-delete ios-apns page and fix stale iOS links…" — address them directly). Re-verified on head 0df4bdd.

✅ Fixed

All 4 old pages now properly deleted — analyzer reports removed: 4 (was removed: 1 with 3 emptied to 0 bytes). No 0-byte .mdx files remain in notifications/.
All 4 deleted URLs have working redirects ([2a] 0 of 4 unredirected) — and now that the files are genuinely gone, the redirects will actually fire:
- flutter-push-notifications-android / -ios → flutter-push-notifications
- ios-apns-push-notifications / ios-fcm-push-notifications → ios-push-notifications
Broken in-content link fixed — [4] 0 broken links (was 1); push-overview.mdx now links directly to /notifications/ios-push-notifications.
0 nav breaks. (The /notifications/overview orphan is pre-existing — not this PR.)

Combined with the already-verified merged content (proper frontmatter, single consistent version pin cometchat_push_notifications: ^1.0.1, no placeholders/contradictions), the consolidation is now correct end-to-end.

Nicely done on the redirect coverage. Ready to merge. 🚀

_{🤖 Automated docs review — re-check after fixes.}

The push-getting-started page is introduced by the still-open Flutter PR #440; until it merges, link the shared setup prerequisite to the existing notifications/push-overview page so the RN guide has no dead links on main. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…uide Checked every claim against the package source; two were wrong. iOS — the guide told apps to hand-write a PKPushRegistry and the four delegate methods in AppDelegate, AFTER adding the setup CLI's generated file to the target. That file already owns the registry (on a background queue) and forwards all four events. Doing both is a compile error (didRegisterForRemoteNotifications… defined twice) or two registries, which double-delivers every VoIP push. And the one line an app actually needs, `CometChatVoIP.shared.register()`, was never mentioned. Replaced with that line, a warning against a second registry and on clashing with existing delegate methods, and a note for Objective-C AppDelegates. Android — the guide told apps to add firebase-bom + firebase-messaging. The package already depends on both; only the google-services plugin is needed. Updated the quick reference, the section 6 cold-start warning and four troubleshooting rows that repeated those instructions or the old logout helper. Structure, against Flutter's unified guide (#440): - Badge: add the dashboard step that enables unreadMessageCount, and order tabs Android → iOS like every other tab group. - Testing: add a fresh-install check (Flutter has a reinstall item) and a logout check. Sections 3 and 4 keep a single code path rather than Flutter's per-platform tabs: Flutter's init and token registration genuinely differ per platform, while this package's are one identical JS call on both. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Updated Migration Guide

c30810e

raj-cometchat requested a review from jitvarpatil July 27, 2026 05:32

raj-cometchat self-assigned this Jul 27, 2026

raj-cometchat requested a review from mathews-cometchat as a code owner July 27, 2026 05:32

mintlify Bot deployed to staging July 27, 2026 05:37 View deployment

Updated Push Notifications section

d3364a2

mintlify Bot deployed to staging July 27, 2026 13:15 View deployment

Added getting started

1ac9251

mintlify Bot deployed to staging July 27, 2026 13:35 View deployment

Updated code

83e29ad

mintlify Bot deployed to staging July 27, 2026 13:41 View deployment

Merged Flutter android and ios

ae27153

mintlify Bot deployed to staging July 27, 2026 14:52 View deployment

Updated version

0e38f6b

mintlify Bot deployed to staging July 28, 2026 07:52 View deployment

Added resources in Flutter

6d67f35

raj-cometchat requested review from adityakotasthane07, ashfaqcometchat and raj-dubey1 July 28, 2026 08:12

mintlify Bot deployed to staging July 28, 2026 08:12 View deployment

ashfaqcometchat changed the title ~~Updated Migration Guide~~ Updated Integration Guide Jul 28, 2026

raj-dubey1 previously approved these changes Jul 28, 2026

View reviewed changes

ashfaqcometchat and others added 2 commits July 28, 2026 15:37

Merge pull request #444 from cometchat/docs/android-push-notification…

482f595

…s-sdk Rewrite Android push guide for drop-in push-notifications-android SDK

ashfaqcometchat dismissed raj-dubey1’s stale review via 482f595 July 28, 2026 10:18

mintlify Bot deployed to staging July 28, 2026 10:19 View deployment

fix

bb76667

mintlify Bot deployed to staging July 28, 2026 10:56 View deployment

ashfaqcometchat previously approved these changes Jul 28, 2026

View reviewed changes

adityakotasthane07 dismissed ashfaqcometchat’s stale review via e55fa4c July 28, 2026 13:33

mintlify Bot deployed to staging July 28, 2026 13:36 View deployment

Revert unrelated link change in sdk/ios/2.0/extensions.mdx

72e281d

The legacy 2.0 extensions page is out of scope for the push SDK rewrite; the redirect on the old slug handles the old link.

mintlify Bot deployed to staging July 28, 2026 14:38 View deployment

shardul-cometchat previously approved these changes Jul 28, 2026

View reviewed changes

ashfaqcometchat previously approved these changes Jul 31, 2026

View reviewed changes

adityakotasthane07 previously approved these changes Aug 7, 2026

View reviewed changes

resolved conflicts

6b44f2f

DhruvKushvaha2004 dismissed stale reviews from adityakotasthane07, ashfaqcometchat, and shardul-cometchat via 6b44f2f August 7, 2026 15:33

mintlify Bot deployed to staging August 7, 2026 15:36 View deployment

adityakotasthane07 added 3 commits August 10, 2026 12:28

adityakotasthane07 self-requested a review August 10, 2026 09:17

adityakotasthane07 approved these changes Aug 10, 2026

View reviewed changes

jitvarpatil approved these changes Aug 10, 2026

View reviewed changes

suraj-chauhan-cometchat mentioned this pull request Aug 28, 2026

docs(rn): unify React Native push notifications into a single guide #486

Open

Navigation Menu

Uh oh!

Updated Integration Guide - #440

Updated Integration Guide#440
raj-cometchat wants to merge 16 commits into
mainfrom
docs/new-flutter-push-notifications

raj-cometchat commented Jul 27, 2026 •

edited by ashfaqcometchat

Loading

Uh oh!

mintlify Bot commented Jul 27, 2026

Uh oh!

mintlify Bot commented Jul 27, 2026

Uh oh!

jitvarpatil commented Aug 10, 2026

Uh oh!

jitvarpatil commented Aug 10, 2026

Uh oh!

jitvarpatil left a comment

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

7 participants

Uh oh!

Conversation

raj-cometchat commented Jul 27, 2026 • edited by ashfaqcometchat Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Related Issue(s)

Type of Change

Checklist

Additional Information

Screenshots (if applicable)

Uh oh!

mintlify Bot commented Jul 27, 2026

Uh oh!

mintlify Bot commented Jul 27, 2026

Uh oh!

jitvarpatil commented Aug 10, 2026

Docs review — 🟠 Request changes

🟠 P1 — 3 old pages emptied instead of deleted (breaks their own redirects)

🟠 P1 — in-content link to a deleted page

✅ What passed

Uh oh!

jitvarpatil commented Aug 10, 2026

Re-review — ✅ Approve

✅ Fixed

Uh oh!

jitvarpatil left a comment

Choose a reason for hiding this comment

Re-review — ✅ Approve

✅ Fixed

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

7 participants

raj-cometchat commented Jul 27, 2026 •

edited by ashfaqcometchat

Loading