You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For our prod environment, it is fixed after deploy so we were able to copy it, but for the local development, it is a dynamic ngrok url. How can we get that value in our code?
I see getBotSiteEndpoint here in some test code that parses the config file, is that the only way?
The text was updated successfully, but these errors were encountered:
Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.
In Teams Toolkit V4, you can obtain the dynamic ngrok URL either by accessing the ngrok web interface (sample code) or retrieving it from the .fx\states\state.local.json file.
In Teams Toolkit V5, it's possible to modify the teamsapp.local.yml file and include the BOT_ENDPOINT within the runtime environment variables.
For our prod environment, it is fixed after deploy so we were able to copy it, but for the local development, it is a dynamic ngrok url. How can we get that value in our code?
I see getBotSiteEndpoint here in some test code that parses the config file, is that the only way?
The text was updated successfully, but these errors were encountered: