Skip to main content
The CometChatCardBubble component renders a developer Card Message (message.getCategory() === "card") as a card bubble inside a conversation. It is the card equivalent of the text bubble: the surrounding CometChatMessageList bubble supplies the container, receipts, reactions, options, reply and thread view — this component only replaces the content view with the rendered card.

Overview

The UI Kit is a render-only consumer of cards: it draws cards delivered by the SDK and forwards card actions to your app. It never parses or mutates the card body, and never sends or creates cards. When a card message arrives, the UI Kit routes it to this bubble automatically. The component follows a strict render-only contract:
  • Render-only — the raw card payload from message.getCard() (or the raw data.card) is serialized verbatim and handed to the prebuilt CometChatCardView renderer (from @cometchat/cards-react) as a cardJson string. The UI Kit performs zero transformation of the payload.
  • No behavior — the bubble runs no action logic of its own. When a user taps an interactive element, the renderer’s raw action is pure-forwarded on two channels (see Card Actions); your app owns all behavior.
  • Graceful fallback — when the payload is empty or invalid, a single-line fallback text is shown instead of an empty bubble (see Fallback Behavior).
Card rendering (layout, theming, interactive elements) is owned by the prebuilt @cometchat/cards-react renderer library, not by the UI Kit. The UI Kit is responsible only for delivering the payload to the renderer and forwarding actions back out.

Automatic Rendering

In the standard chat flow you do not instantiate this component yourself. CometChatMessageList routes any message with category "card" to CometChatCardBubble automatically, keyed by category (the developer type is arbitrary). To handle card actions in this flow, subscribe to the ccCardActionClicked event bus — no component wiring is required. Use the component directly only when you are building a fully custom message renderer.

Basic Usage

Incoming vs Outgoing Messages

isSentByMe toggles the outgoing (sender) vs incoming (receiver) styling, mirroring the text bubble.

Props

The renderer theme is resolved automatically from CometChatUIKit.themeMode — there is no themeMode prop. To restyle the rendered card, theme the @cometchat/cards-react renderer directly.

Card Actions

The Cards renderer is a pure renderer — it emits actions through a callback without executing them. The bubble forwards each action on both channels and runs no behavior of its own:
  1. onCardAction prop — for apps that render this bubble directly.
  2. CometChatUIEvents.ccCardActionClicked event bus — for the standard, internally rendered flow where the bubble is created by the UI Kit. This is the recommended channel for the default message list.
Act on one channel only to avoid double-handling the same tap. In the standard CometChatMessageList flow, use the ccCardActionClicked bus.

Handling actions via the prop

Handling actions via the event bus

The full set of action types and a complete reference handler are covered in the Card Messages guide.

Fallback Behavior

When the payload is empty or invalid (null, a blank string, or an empty object), the bubble renders a single line of fallback text instead of an empty card. The fallback is resolved in this order:
  1. message.getFallbackText()
  2. message.getText()
  3. Localized "Card Message" (the card_message localization key)
This keeps the conversation readable even if a card payload is malformed or a client cannot render it.

Customization

The card’s internal layout, colors, and typography are controlled by the @cometchat/cards-react renderer. The bubble wrapper and fallback line are styled with CSS variables:
To restyle the rendered card itself (button colors, header, body), theme the renderer rather than overriding CSS — the card DOM is owned by @cometchat/cards-react.

Technical Details

  • Content-view component — rendered as the contentView of the developer card message template, so it inherits the full bubble (status info, reply view, reactions, options).
  • Renderer dependencyCometChatCardView from @cometchat/cards-react.
  • Callback before schema — the renderer’s onAction callback is bound before cardJson is rendered, so actions are captured from the first tap.
  • Theme — the renderer themeMode is taken from CometChatUIKit.themeMode.
  • Card Messages guide — the full card rendering implementation: developer cards, agent cards, streaming cards, and the complete action vocabulary.
  • CometChatMessageList — routes card messages to this bubble.
  • CometChatMessageTemplate — the template that maps category: "card" to this bubble.
  • Events — the ccCardActionClicked event reference.