Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pages.config.setConfig is saving wrong config webhookUrl in new client #2290

Open
vbatr opened this issue Apr 24, 2024 · 4 comments
Open

pages.config.setConfig is saving wrong config webhookUrl in new client #2290

vbatr opened this issue Apr 24, 2024 · 4 comments
Assignees
Labels
bug T2.1 teams issue issue that has been reviewed and likely teams specific

Comments

@vbatr
Copy link

vbatr commented Apr 24, 2024

Hi all,

When I am trying to save setting configuration while configuring new connector the different webhookUrl is set on calling pages.config.setConfig(), so when I am trying to manage the saved connector setting it has different webhook URL

STR:

  1. Create connector
  2. Get webhook URL by calling await microsoftTeams.pages.getConfig()
  3. Save configs by calling pages.config.setConfig()
  4. Open configured connector and check received webhook URL ((await microsoftTeams.pages.getConfig()).webhookURL)

AR:
The webhook URL on configuration pages doesn't much webhook URL after saving configs
ER:
webhook URL should be the same

Teams client: Teams v2
msteams-js version: 2.22.0

Notes:

Everything is working as expected on Teams legacy client. The webhook URL is the same after saving configs

Regards,
Volodymyr B.

@maglims maglims added the teams issue issue that has been reviewed and likely teams specific label Apr 24, 2024
@Meghana-MSFT
Copy link

Could you please confirm if you are facing the same issue while creating this manually as well? Is your issue similar to https://learn.microsoft.com/en-us/answers/questions/1621849/when-edit-an-existing-configured-connector-in-new?

@Meghana-MSFT
Copy link

@vbatr - Could you please confirm above?

@vbatr
Copy link
Author

vbatr commented Apr 29, 2024

Hi @Meghana-MSFT

It seems that issue described in the question is related to the same issue - pages.config.setConfig() is generating new configuration and webhhok URL is changing, that is causing new configuration creation.

@Meghana-MSFT
Copy link

We already have an incident created for this issue. We will keep you posted on the updates. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug T2.1 teams issue issue that has been reviewed and likely teams specific
Projects
None yet
Development

No branches or pull requests

4 participants