Attachments with incorrect base64 contentUrl in sendActivity fails silently

Open

#159 opened on Oct 31, 2018 8 comments 0 reactions 1 assignee View on GitHub

@ckkashyap is already working on this.

Since Feb 6, 2019.

Assessment

This issue has not been assessed yet.

Description

Versions

What package version of the SDK are you using: 4.0.8 (botbuilder, botbuilder-dialogs)
What nodejs version are you using: v.8.12.0
What browser version are you using: Chrome v69
What os are you using: Windows 10

Describe the bug

When trying to create an attachment that is intentionally corrupt (via an incorrect base64 url), the bot fails silently without throwing an error.

To Reproduce

Create bot with command to trigger send activity with an attachment with the following code:

  try {
    console.log('Start');

    await context.sendActivity({
      type: 'message',
      attachments: [{
        contentType: 'text/plain',
        contentUrl: 'data:image/png;base64,abc\nabc',
        name: 'dot.png'
      }]
    });

    console.log('Succeeded');
  } catch (err) {
    console.log(err);
    throw err;
  }

And on the BotFrameworkAdapter instance, register an onTurnError handler like so:

adapter.onTurnError = async (context, error) => {
  console.log(error);
  await context.sendActivity(`Sorry, ran into an error!\n  ${ error.message }`);
}

Run bot, send command utterance to send activity
Sending the command failed
Note that there is no error in the console, and the line console.log("Succeeded"); is never reached. Similarly, onTurnError is never triggered.

The message fails silently, and after timing out, the Web Chat instance logs a 502 Bad Gateway error.

Sending other messages pass through successfully.

Expected behavior

Since the contentUrl is invalid, the bot should try and catch an error when this command is initiated.

[bug]

Dominant language: TypeScript
Stars: 199
Forks: 133
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

docs: manual client injection examples reference removed exports Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

vitejs/devtools#589 · 1 comment · Opened Sep 25, 2026
🔒 [IBM OSPO Security Notification] — IBM/node-sdk-core Open

security

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

IBM/node-sdk-core#373 · Opened Sep 25, 2026
[fullsend] E2E: topology — Tekton pipeline status decorator timeout on Topology tab Open

e2e-failure ready-to-code

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

redhat-developer/rhdh-plugin-export-overlays#3937 · Opened Sep 25, 2026
The open-first recovery advice falls back to --base main, contradicting the fetched base Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

victorstein/herdr-plugin-pipeline#121 · Opened Sep 25, 2026
Finish the #680 label rename: audit-report 'Layout flags' heading and CLAUDE.md Open

chore

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

offlinecv/OfflineCV#1018 · Opened Sep 25, 2026

More TypeScript issues