[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFHB18QSFB50GG35YY94TT":3,"skill-same:01M6MFHB18QSFB50GG35YY94TT":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MFHB18QSFB50GG35YY94TT","cometchat-react-native-push",null,"Push notifications for CometChat in React Native — FCM on Android, APNs on iOS, registering the device token with CometChatNotifications, and why none of it can be verified without a real device. Triggers: CometChat push notifications React Native, FCM CometChat RN, APNs chat notifications, notifications not arriving React Native, VoIP call push RN.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-push\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"cometchat react native push","cometchat","push","react native","react","native","messaging","notifications","why","token","react-native","verified","for","firebase","triggers","call","apns","push notifications","can","chat","with","2026-11-10 10:12:30",false,"---\nname: cometchat-react-native-push\ndescription: \"Push notifications for CometChat in React Native — FCM on Android, APNs on iOS, registering the device token with CometChatNotifications, and why none of it can be verified without a real device. Triggers: CometChat push notifications React Native, FCM CometChat RN, APNs chat notifications, notifications not arriving React Native, VoIP call push RN.\"\nlicense: \"MIT\"\ncompatibility: \"React Native >=0.77; @cometchat\u002Fchat-sdk-react-native ^4.0.28; @react-native-firebase\u002Fmessaging\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"chat cometchat react-native push notifications fcm apns voip token\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-sdk-react-native@4` + catalog `rn-sdk-v4.json` +\n> `features.rn-v5.json` → `push-notifications`. Docs:\n> `\u002Fnotifications\u002Freact-native-push-notifications-android` · `...-ios`.\n> This skill is **docs-first** — fetch the current setup steps; do not bake a Firebase tutorial.\n\n## Companion skills (read first)\n- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.\n\n## Use this skill when\n- \"add push notifications\" · \"notifications aren't arriving\" · \"VoIP call push\" · \"register the FCM token\"\n\n## Prerequisites & install\n\nPush is **not** web push. There is no service worker. React Native uses the OS transports:\n\n| Platform | Transport | Needs |\n|---|---|---|\n| Android | **FCM** | `google-services.json` in `android\u002Fapp\u002F` |\n| iOS | **FCM (via Firebase → APNs)** | `GoogleService-Info.plist`, an APNs key uploaded to the dashboard, Push capability in Xcode |\n\nEnable Push Notifications in the CometChat dashboard **first** and add the provider for the right\nplatform. With `@react-native-firebase\u002Fmessaging`, **both** Android and iOS use the **FCM** provider —\nFirebase relays to APNs on iOS and hands your app an FCM token, so you register it with CometChat as an\nFCM platform (see below). A raw-APNs (`APNS_REACT_NATIVE_*`) provider is only for a hand-rolled PushKit \u002F\nnative-APNs setup that skips Firebase.\n\n## The wiring — three steps, in this order\n\n1. **`init()` → `login()` must have completed.** A token registered before login belongs to nobody.\n2. **Get the device token** from your messaging library (typically `@react-native-firebase\u002Fmessaging`).\n3. **Register it with CometChat:**\n\n```\nCometChatNotifications.registerPushToken(token, CometChatNotifications.PushPlatforms.FCM_REACT_NATIVE_ANDROID, providerId)\n```\n\nPlatform constants match the token you actually hold. Because the Firebase library above yields an\n**FCM** token on **both** platforms, use `PushPlatforms.FCM_REACT_NATIVE_ANDROID` on Android and\n`PushPlatforms.FCM_REACT_NATIVE_IOS` on iOS (verified in `@cometchat\u002Fchat-sdk-react-native` `CometChat.d.ts`).\nThe `APNS_REACT_NATIVE_DEVICE` \u002F `APNS_REACT_NATIVE_VOIP` constants are ONLY for a raw APNs device\u002FVoIP\ntoken from a hand-rolled PushKit setup — do **not** use them with a Firebase FCM token. **Fetch the exact\nargument order from the docs page for that platform.** `CometChatNotifications`, `registerPushToken`,\n`unregisterPushToken` and `PushPlatforms` are all verified present in `catalogs\u002Frn-sdk-v4.json`.\n\n4. **Unregister on logout** — `unregisterPushToken()`. Skipping this is why a shared or re-used device\nkeeps delivering the previous user's notifications.\n\n## Token refresh is not optional\nDevice tokens rotate. Subscribe to your messaging library's token-refresh event and re-register, or\npush silently stops working days later for a subset of users — the hardest push bug to diagnose\nbecause nothing fails at the time.\n\n## VoIP \u002F call notifications\nCalls need a **data-only** push plus a native dialer integration (CallKeep) so the device rings while\nthe app is killed. That is a materially bigger build than message push, with its own iOS entitlements.\nFetch `\u002Fnotifications\u002Freact-native-push-notifications-android` and `...-ios` and follow them — do not\nimprovise it.\n\n## Why this cannot be smoke-tested\nPush requires a real device (or an emulator image **with Play services** for FCM), real credentials,\nand the app in background or killed. It cannot be verified headlessly, in CI, or on an iOS simulator.\n`features.rn-v5.json` marks it accordingly — treat a \"works\" claim without device evidence as unproven.\n\n## Common pitfalls\n1. **Registering before login** — the token is attached to no user.\n2. **Not unregistering on logout** — the next user gets the previous user's pushes.\n3. **Ignoring token refresh** — push dies quietly, later.\n4. **Wrong platform constant** — registration succeeds, delivery never happens.\n5. **Missing `google-services.json` \u002F `GoogleService-Info.plist`** — build or registration failure.\n6. **Testing on an iOS simulator** — APNs does not work there.\n7. **Expecting message-push setup to cover calls** — VoIP needs data-only push + CallKeep.\n\n## Verify it works\n- Every emitted symbol is in `catalogs\u002Frn-sdk-v4.json`.\n- Dashboard: push enabled, correct provider added for the platform.\n- **On a real device:** notification arrives with the app backgrounded **and** killed; tapping it opens\n  the right conversation; after logout the device stops receiving that user's notifications.\n","> **Ground truth:** `@cometchat\u002Fchat-sdk-react-native@4` + catalog `rn-sdk-v4.json` +\n> `features.rn-v5.json` → `push-notifications`. Docs:\n> `\u002Fnotifications\u002Freact-native-push-notifications-android` · `...-ios`.\n> This skill is **docs-first** — fetch the current setup steps; do not bake a Firebase tutorial.\n\n## Companion skills (read first)\n- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.\n\n## Use this skill when\n- \"add push notifications\" · \"notifications aren't arriving\" · \"VoIP call push\" · \"register the FCM token\"\n\n## Prerequisites & install\n\nPush is **not** web push. There is no service worker. React Native uses the OS transports:\n\n| Platform | Transport | Needs |\n|---|---|---|\n| Android | **FCM** | `google-services.json` in `android\u002Fapp\u002F` |\n| iOS | **FCM (via Firebase → APNs)** | `GoogleService-Info.plist`, an APNs key uploaded to the dashboard, Push capability in Xcode |\n\nEnable Push Notifications in the CometChat dashboard **first** and add the provider for the right\nplatform. With `@react-native-firebase\u002Fmessaging`, **both** Android and iOS use the **FCM** provider —\nFirebase relays to APNs on iOS and hands your app an FCM token, so you register it with CometChat as an\nFCM platform (see below). A raw-APNs (`APNS_REACT_NATIVE_*`) provider is only for a hand-rolled PushKit \u002F\nnative-APNs setup that skips Firebase.\n\n## The wiring — three steps, in this order\n\n1. **`init()` → `login()` must have completed.** A token registered before login belongs to nobody.\n2. **Get the device token** from your messaging library (typically `@react-native-firebase\u002Fmessaging`).\n3. **Register it with CometChat:**\n\n```\nCometChatNotifications.registerPushToken(token, CometChatNotifications.PushPlatforms.FCM_REACT_NATIVE_ANDROID, providerId)\n```\n\nPlatform constants match the token you actually hold. Because the Firebase library above yields an\n**FCM** token on **both** platforms, use `PushPlatforms.FCM_REACT_NATIVE_ANDROID` on Android and\n`PushPlatforms.FCM_REACT_NATIVE_IOS` on iOS (verified in `@cometchat\u002Fchat-sdk-react-native` `CometChat.d.ts`).\nThe `APNS_REACT_NATIVE_DEVICE` \u002F `APNS_REACT_NATIVE_VOIP` constants are ONLY for a raw APNs device\u002FVoIP\ntoken from a hand-rolled PushKit setup — do **not** use them with a Firebase FCM token. **Fetch the exact\nargument order from the docs page for that platform.** `CometChatNotifications`, `registerPushToken`,\n`unregisterPushToken` and `PushPlatforms` are all verified present in `catalogs\u002Frn-sdk-v4.json`.\n\n4. **Unregister on logout** — `unregisterPushToken()`. Skipping this is why a shared or re-used device\nkeeps delivering the previous user's notifications.\n\n## Token refresh is not optional\nDevice tokens rotate. Subscribe to your messaging library's token-refresh event and re-register, or\npush silently stops working days later for a subset of users — the hardest push bug to diagnose\nbecause nothing fails at the time.\n\n## VoIP \u002F call notifications\nCalls need a **data-only** push plus a native dialer integration (CallKeep) so the device rings while\nthe app is killed. That is a materially bigger build than message push, with its own iOS entitlements.\nFetch `\u002Fnotifications\u002Freact-native-push-notifications-android` and `...-ios` and follow them — do not\nimprovise it.\n\n## Why this cannot be smoke-tested\nPush requires a real device (or an emulator image **with Play services** for FCM), real credentials,\nand the app in background or killed. It cannot be verified headlessly, in CI, or on an iOS simulator.\n`features.rn-v5.json` marks it accordingly — treat a \"works\" claim without device evidence as unproven.\n\n## Common pitfalls\n1. **Registering before login** — the token is attached to no user.\n2. **Not unregistering on logout** — the next user gets the previous user's pushes.\n3. **Ignoring token refresh** — push dies quietly, later.\n4. **Wrong platform constant** — registration succeeds, delivery never happens.\n5. **Missing `google-services.json` \u002F `GoogleService-Info.plist`** — build or registration failure.\n6. **Testing on an iOS simulator** — APNs does not work there.\n7. **Expecting message-push setup to cover calls** — VoIP needs data-only push + CallKeep.\n\n## Verify it works\n- Every emitted symbol is in `catalogs\u002Frn-sdk-v4.json`.\n- Dashboard: push enabled, correct provider added for the platform.\n- **On a real device:** notification arrives with the app backgrounded **and** killed; tapping it opens\n  the right conversation; after logout the device stops receiving that user's notifications.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":54},{"tags":51,"author":52,"version":53},"chat cometchat react-native push notifications fcm apns voip token","CometChat","1.0.0","React Native >=0.77; @cometchat\u002Fchat-sdk-react-native ^4.0.28; @react-native-firebase\u002Fmessaging","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-push",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-push",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-push",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-push","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-push\u002FSKILL.md",true,[],[80,89,97,105,113,121],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]