Missing Culture Key in Microsoft Teams
See original GitHub issueDescribe the bug
We’re trying to build a Microsoft Teams bot using the Composer app to design conversational flows and manage our LUIS application. When testing it in the Emulator and on our company Teams we have to set both the Emulator and the Teams languages to english (US) even if in the app.settings we have specified the default language “it-it” for the LUIS app that is created with the correct culture settings. Otherwise, we obtain this error when getting bot replies:
The given key 'it-IT' was not present in the dictionary.
We tried to re-create the LUIS app setting “it-IT” as the language instead of “it-it” but we obtain the following error during the deploy procedure:
The application version culture must be the same as the application culture.
What we noticed is that teams is looking for culture in format “en-US” or “en-GB” but in the LUIS portal and from the Composer app only all lower case cultures are accepted.
Version
Latest stable
Browser
- Chrome
- Safari
- Firefox
- Edge
OS
- macOS
- Windows
- Ubuntu
Expected behavior
We expected to have coherent culture settings. We couldn’t find any information about this in the docs.
Screenshots
Additional context
The same problem that is affecting Teams is also affecting the Emulator in which we can test our bot only using en-US as locale.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (7 by maintainers)
Top GitHub Comments
@eluchsinger, @fathorMB , the multi-language feature is already merged in to main branch, could you have a try and let us know if there is any issues in your scenario?
@luhan2017 do you have a tracking item for the multi-language support? And what does multi-language mean for you? Is it just changing the bot language to something different, than en-us or having a bot with multiple languages?
Our customer’s bot has got the requirement that is has to be in german. When is R10 due? I believe I could build the Composer myself as soon as the PR is merged into master, if we can’t wait for R10…