walletSendCalls content is undefined after fetching messages in @xmtp/browser-sdk 6.1.2

[chopperdaddy]

Source

Browser SDK

Describe the bug

After updating to @xmtp/browser-sdk 6.1.2, messages with walletSendCalls content type have undefined content when fetched via conversation.messages().

The warning No codec found for content type 'xmtp.org/walletSendCalls:1.0' appears in the console.

Structured logs show the correct data. Also affects xmtp.chat.

Steps to reproduce the bug

• Update to @xmtp/browser-sdk 6.1.2
• Send or receive a message with walletSendCalls content type
• Fetch messages using conversation.messages()
• Access message.content for the walletSendCalls message

Code of conduct

• I agree to follow the XMTP code of conduct

[chopperdaddy]

I've fixed this by manually registering the codec in client options:

private clientOptions: ClientOptions = {
  ...,
  codecs: [new WalletSendCallsCodec()]
};

[rygine]

@chopperdaddy registering the codec should not be necessary unless there's a bug. can you point me to the code (or share here) that's sending the walletSendCalls content?

[github-actions]

There has been no activity on this issue. It will be closed in 7 days if there is no new activity.

[chopperdaddy]

@chopperdaddy registering the codec should not be necessary unless there's a bug. can you point me to the code (or share here) that's sending the walletSendCalls content?

That was also my understanding when upgrading to v6.1.2, but the only "fix" was manually registering the codec. Also appears to happen with transactionReference.

Here is the content from walletSendCalls (although it happens with any walletSendCalls content)

{
    "content": {
        "version": "1.0",
        "from": "0xf1a...6c7",
        "chainId": "0x2105",
        "calls": [
            {
                "to": "0x0000...",
                "data": "0x2213bc...",
                "gas": "0xa4110",
                "metadata": {
                    "description": "Swap 10000 BANKR to DRB"
                },
                "value": "0x0"
            }
        ]
    },
    "contentType": {
        "authorityId": "xmtp.org",
        "typeId": "walletSendCalls",
        "versionMajor": 1,
        "versionMinor": 0
    },
    "conversationId": "e8d8fa...",
    "deliveryStatus": 1,
    "fallback": "[Transaction request generated]: {\"version\":\"1.0\",\"from\":\"0xf1...941d...\",\"chainId\":\"0x2105\",\"calls\":[{\"to\":\"0x00000...\",\"data\":\"0x2213bc...\",\"gas\":\"0xa4110\",\"metadata\":{\"description\":\"Swap 10000 BANKR to DRB\"},\"value\":\"0x0\"}]}",
    "id": "78dc...",
    "kind": 0,
    "numReplies": 0,
    "reactions": [],
    "_rawReactions": [],
    "senderInboxId": "062b...",
    "sentAt": "2026-01-26T18:19:37.001Z",
    "sentAtNs": 1769451577001137000,
    "senderAddress": "0x7f1c...",
    "self": false
}

[github-actions]

There has been no activity on this issue. It will be closed in 7 days if there is no new activity.

[github-actions]

Closed due to inactivity. If still interested, please reopen and continue the discussion.

[bennycode]

@chopperdaddy thanks for your report. Is it still happening? We’ve observed similar behavior with Agent SDK v2.1.0 showing:

No codec found for content type "xmtp.org/transactionReference:1.0"

[github-actions]

There has been no activity on this issue. It will be closed in 7 days if there is no new activity.