getTabInstances() sometimes fails to populate critical fields on some tabs.

[ascott18]

When calling getTabInstances, we have observed that sometimes the results for some tabs are missing critical fields like channelId and teamId.

• This doesn't happen on every call - I haven't been able to determine a pattern for why/when it happens.
• When it happens, it seems to always be the same tab instances that fail. The issue never occurs "partially" - either all the tabs that have the issue are missing these values, or no tabs are missing these values.

See the null values marked with red below:

[sayali-MSFT]

Hello @ascott18 ,Thank you for reaching out!
To assist you better, could you please provide the following details?

1. Reproduction Steps: Please share the steps you took to encounter the issue.
2. Documentation Links: Any specific documentation you followed that relates to your problem.
3. Teams Client Version: What version of the Teams client are you using?
4. Code Snippets: Relevant code snippets that illustrate the issue.
5. Manifest Package: If applicable, please share the manifest package for your app.

This information will help us better understand the situation and provide a more accurate response.

[ascott18]

Repro steps

1. Call const tabs = await microsoftTeams.pages.tabs.getTabInstances({ favoriteChannelsOnly: false, favoriteTeamsOnly: false })
2. Observe that some tabs in the results are sometimes missing some information, seemingly at random.

Documentation

https://learn.microsoft.com/en-us/javascript/api/@microsoft/teams-js/pages.tabs?view=msteams-client-js-latest#@microsoft-teams-js-pages-tabs-gettabinstances

Teams Version

26058.706.4496.6424

Code Snippets

const tabs = await microsoftTeams.pages.tabs.getTabInstances({ favoriteChannelsOnly: false, favoriteTeamsOnly: false })

[sayali-MSFT]

Hello @ascott18 .Thank you for sharing the information. We will try it on our end and get back to you. If it is a bug, we will raise it accordingly.

[sayali-MSFT]

Hello @ascott18,
Thank you for your patience! We were able to reproduce the issue. We have reported this as a bug for further investigation.

We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!