Unhandled promise rejection somewhere in people.get

[brettdh]

Describe the bug
When an SDK method (such as webex.people.get(personId)) fails with an error, I expect the promise returned by the method to reject, which it does. However, some other promise inside the SDK is also rejecting, as shown in the browser console log and also in the dev server's built-in error handling, which detects the unhandled promise rejection and displays the error (in this case, just the person ID with no other context) in the full-screen overlay.

The reason I know that this is an issue inside the SDK and not in my code is that if I replace this call in my code:

await webex.people.get(personId)

with this:

throw new Error('whoopsie')

then the unhandled rejections go away. This indicates that the error handling in my app is working correctly and that the problem is in the SDK, perhaps with a broken chain of promises somewhere.

To Reproduce
Steps to reproduce the behavior:

1. Create a browser app that calls webex.people.get(personId) with a `personId that doesn't exist
2. Run the app in a browser
3. Observe the unhandled promise rejection in the browser console

Expected behavior
No unhandled rejections from within the SDK

Platform (please complete the following information):

• OS: macOS Tahoe 26.1
• Browser: Chrome
• Version: 142.0.7444.176
• Device Type: Desktop

[sandiban]

Hi @brettdh,
Could you kindly share us the complete browser HAR logs for this item.
Also wanted to understand before that, were you able to reproduce the issue over the JS SDK sample - https://web-sdk.webex.com/samples/browser-plugin-meetings/, if not could you kindly try once from the sample App please and if the unhandled exception still comes, kindly share the corresponding HAR logs for it.
And one more thing, are you using for personal Bearer Access token or, JWT token for authorization? Kindly confirm please. Thanks!

[brettdh]

As far as I can tell, there's no sample app at https://web-sdk.webex.com/samples that demonstrates broad use of the messaging SDK - specifically, the call to webex.people.get(personId) that I mentioned above.

I am using the bearer access token.

I cannot share a HAR or the source code for this app, but here is a minimal repro using webex-node (though I reported this bug with the browser SDK, the result is the same in NodeJS):

import Webex from 'webex-node';

const webex = Webex.init({
  credentials: {
    access_token: process.env.WEBEX_ACCESS_TOKEN
  },
  config: {
    credentials: {
      clientType: 'public'
    },
  }
});

process.on('unhandledRejection', (reason, promise) => {
    // this should not be reached, but the webex SDK is not handling all promise rejections
    console.error('Unhandled Rejection at:', promise, 'reason:', reason);
});

try {
    const uuid = crypto.randomUUID();
    const personId = new Buffer(`ciscospark://us/PEOPLE/${uuid}`).toString('base64').replace(/=/g, '');
    console.log('Fetching person with ID:', personId);
    console.log('Fetching person with UUID:', uuid);
    await webex.people.get(personId);
} catch (e) {
    console.error('Error fetching person:', e);
}

and the output:

Error fetching person: Y2lzY29zcGFyazovL3VzL1BFT1BMRS82MTNlOGVmOS0wY2Q3LTQ3MzAtOGY3Ny00MTJhNzVlMzdjNjQ
Unhandled Rejection at: Promise {
  <rejected> 'Y2lzY29zcGFyazovL3VzL1BFT1BMRS82MTNlOGVmOS0wY2Q3LTQ3MzAtOGY3Ny00MTJhNzVlMzdjNjQ'
} reason: Y2lzY29zcGFyazovL3VzL1BFT1BMRS82MTNlOGVmOS0wY2Q3LTQ3MzAtOGY3Ny00MTJhNzVlMzdjNjQ

[jbenyovs]

@brettdh I was able to reproduce this issue with using your repro file as a basis for a simple browser app. Reported it to engineering.