-
Notifications
You must be signed in to change notification settings - Fork 192
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
Comments
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? |
@vbatr - Could you please confirm above? |
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. |
We already have an incident created for this issue. We will keep you posted on the updates. Thank you. |
Have there been any updates to this? It's causing issues for our current connector as well. The only workaround we've found is to have users navigate to the Manage page where we can get the actual webhook URL and save it on our side. |
Unfortunately, we do not have any updates to share. We are following up with engineering team for updates. |
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:
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.
The text was updated successfully, but these errors were encountered: