Forum Discussion
ms-user-1
May 03, 2024Copper Contributor
Connector Compatibility Issues with Updated Microsoft Teams
Hi,
We have been successfully using our app connector for several years without issues. However, since upgrading to the latest version of Microsoft Teams, we have encountered significant functionality problems that were not present in the older version.
While the connector continues to work flawlessly on the older version of MS Teams, it fails to configure or remove connectors in the new MS Teams. Additionally, the webhook functionality is also non-operational.
We have noticed missing context values such as 'teamName' and 'teamId', which may be contributing to these issues. I have attached screenshots below for your review.
Old MS Teams context
Old ms teams context
New MS Teams context 
New ms teams context
Furthermore, we are experiencing problems with the microsoftTeams.settings.setSettings() function from the Deleted/teams-js library, which does not seem to operate correctly in the new MS Teams environment. It is unclear whether this issue is related to the saveEvent.notifySuccess() function or if there are other underlying problems preventing the settings from being applied properly.
Many of our clients are expressing their frustration due to these disruptions. We are eager for your assistance and look forward to your swift response to help resolve these issues.
Best regards,
- ChetanSharma-msft
Microsoft
Hello ms-user-1 - Could you please confirm which Teams client library and Teams client versions you are using?
Starting with TeamsJS library v.2.0.0, APIs in the settings namespace have been deprecated in favor of equivalent APIs in the pages namespace, including pages.getConfig() and other APIs in the pages.config sub-namespace.
Please refer this documentation:
https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-creating?view=msteams-client-js-latest - Dinesh-MSFT
Microsoft
Hi ms-user-1 - Thanks for raising the query.
We will look into it and let you know the updates.- SmonnahanCopper Contributor
Dinesh-MSFT What's the status of this because I am also dealing with the same bug and there is no work around to fixing the connectors
- Dinesh-MSFT
Microsoft
Hi Smonnahan
Sorry for the delay in response.
Could you please confirm if you are using incoming webhook or outgoing webhook?
Also, could you please share code snippet of how you are getting the context? So that we will look into it and let you know the update.