User-defined DataMessage callback errors should not be fatal

[schontz]

What happened and what did you expect to happen?

1. subscribeToTranscriptEvent callback received unexpected data and threw an error
2. Actual: The meeting died (fatal error)
3. Expected: The meeting does not die

Have you reviewed our existing documentation?

• [X] GitHub issues
• [X] FAQs page
• [X] README page
• [X] Feature-specific guides

Reproduction steps

Something like this:

subscribeToTranscriptEvent(() => {
  throw new Error('bad callback');
});

Amazon Chime SDK for JavaScript version

main

What browsers are you seeing the problem on?

Chome

Browser version

lateset

Meeting and Attendee ID Information.

No response

Browser console logs

Nothing is logged to the console, because the error is swallowed up. It does exist in the logger because fatal errors are logged there.

[ltrung]

I think it is expected that realtimeAPI throw fatal error though

[ltrung]

Closing as the PR has been merged.