Error: not_specified

[ascott18]

We're seeing the following error in our production logs. Please advise on how we're meant to deal with the "not_specified" error from Teams. Perhaps Teams should generate better error messages?

@microsoft/team-js version: 1.9.0

Error: not_specified
    at webpack:///node_modules/@microsoft/teams-js/dist/MicrosoftTeams.min.js:1:8959
    at apply (webpack:///node_modules/@microsoft/teams-js/dist/MicrosoftTeams.min.js:1:2816)
    at u (webpack:///node_modules/@microsoft/teams-js/dist/MicrosoftTeams.min.js:1:6944)
    at processMessage (webpack:///node_modules/@microsoft/teams-js/dist/MicrosoftTeams.min.js:1:37798)

[ghost]

Hi ascott18! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

[Jagadeesh-MSFT]

Hi @ascott18, could you please explain briefly and share the repro steps to mitigate the issue.

[ascott18]

I have no explanation for this - we're just seeing this error happening for some users in our production logs. This isn't something that our code is doing - as you can see, the stack trace is entirely within Teams code. Teams is throwing useless, nondescriptive errors. We'd like for this issue to be fixed by Microsoft in the event that it is a symptom of something causing an adverse user experience.

[Nikitha-MSFT]

In production logs means are you using developer tools to capture log? Could you please share how you are capturing the logs? Also please specify when you are getting the "not_specified" errors? Are you receiving this on action performed? Could you please explain your scenario in more detail?

[ascott18]

• We're seeing this error in the Application Insights logging that we have running in our app.
• Our end users are encountering this error. We do not have any information about what the users were doing, or even who the users are.
• We're seeing this at all stages of page lifecycle (sometimes a second or two after page load, sometimes several minutes after page load).
• So far, all instances of this error have happened in the Teams desktop app - never on mobile or in the browser.

[Jagadeesh-MSFT]

Hi @ascott18, we are taking this to our internal team, will update you soon.

[Jagadeesh-MSFT]

Hi @ascott18, it seems like there is a bug in your integration with the ApplicationInsights-JS SDK which is resulting in these not_specified errors getting logged. Could you please take a look at this similar issue and double check that you are correctly passing the exception information to the App Insights SDK:
Getting error messages of the format not_specified at e.sendExceptionInternal · Issue #1006

[ascott18]

@Jagadeesh-MSFT We are not manually calling trackException - this is being caught by the passive error catching mechanisms of the AI JS SDK.

[Jagadeesh-MSFT]

Hi @ascott18, we are taking this to our internal team, will update you soon.

[Wajeed-msft]

@ydogandjiev - do you know what might be going wrong here?

[Wajeed-msft]

@ascott18 - we are unable to repro this at our end. Would it be possible for you to get repro steps?

[ascott18]

No. As I previously mentioned,

I have no explanation for this - we're just seeing this error happening for some users in our production logs.

and

Our end users are encountering this error. We do not have any information about what the users were doing, or even who the users are.

Since the stack trace is entirely contained within the Microsoft Teams JS SDK, I would expect that you guys could trace through your own code and see what might be triggering this.

[ChetanSharma-msft]

@ascott18 - We have raised a internal bug for it and engineering team is looking into it

[ydogandjiev]

Spent some more time on this issue today. Pulling up v1.9.0 of the Client SDK in VS Code I looked for the code called out in the exception stack:

And got this:

Which appears to be this code:

microsoft-teams-library-js/src/internal/utils.ts

Line 22 in fef9489

export function getGenericOnCompleteHandler(errorMessage?: string): (success: boolean, reason?: string) => void {

So that means you are most likely calling one of these APIs without specifying a callback:

• settings.setSettings
• executeDeepLink
• postMessage (to task module)

And when the API call fails the generic callback handler throws an exception. @ascott18, can you please try passing your own callback function to these APIs and using it to log a more obvious error message to your traces?

[ghost]

Tell us about your experience!

Hi ascott18! This issue is closed in our system. We would like your feedback on your experience with our support team and Platform.

Best regards,
Teams Platform