Emulator not sending user's Locale in conversationUpdate activities
See original GitHub issueWhen connecting to a bot with the emulator and specifying the Locale
, the conversationUpdate
Activity
that is passed to the bot has a null Locale
. Only when MessageActivity
s are sent is the Locale
specified.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How do I get the locale in conversationUpdate activity?
One solution to get the language of the user before his 1st input is to use the backchannel feature of the Webchat.
Read more >Channels reference - Bot Service - Microsoft Learn
Many channels send conversation update activities. Often, bot welcome behavior is triggered by the conversation update activity. However, ...
Read more >How to receive events in a Bot Framework SDK v4 Web API bot?
How to send proactive messages with Bot Builder v4? ... activities (there's no user for the channel ConversationUpdate activity).
Read more >[Solved]-How do I get the locale in conversationUpdate activity?
getElementById('bot')); // Send message to provide language of user botConnectionSettings.postActivity({ type: 'event', from: { id: 'userid' }, locale: ...
Read more >Known issues - Microsoft Open Source
Emulator will pass the locale setting to the bot as the first ConversationUpdate call. When you're testing in other environments, if it's something...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@stevengum there is already a global locale setting in the Emulator that defaults to
en-US
:So it would be as simple as grabbing the setting value from the settings at the time of sending the conversationUpdate activity and appending it to the activity payload.
We’ll keep this on our long-term backlog. No ETA, but we would happily accept a community contribution.