Localization Change Causes Publishing Problem (also not working on Emulator)

[humak]

Describe the bug

My bot is working properly on the composer web chat whether the default language is English or Turkish. But on Emulator, it is only working properly when the default language is English. When I change the language to Turkish, it is not working on the Emulator.

It also causes problems in the Publishing phase, if the bot is not working on the Emulator, it is not working after publishing too.

Version

Version: 2.1.0-nightly.266986.c355633
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
(experienced the same issue on the stable version too)

Emulator: 4.13.0

Browser

• Edge

OS

• Windows

To Reproduce

Steps to reproduce the behavior:

1. Change your localization settings, make Turkish default language
2. Try on webchat, it will work properly
3. Try on Emulator, it will possibly fail (no answers)
4. Try to publish, if it is successfully published, try from Azure Portal, it will not work properly (no answers)

Screenshots

1. When localization is English: it works on emulator

2. Turkish case: it works on webchat but not on Emulator

Additional context

We spend so much time trying to understand why it fails after publishing and not responds, thats how we discovered that, when it stays on English as default, it works after publishing too, and emulator of course.

[srinaath]

@humak This is an emulator setting that needs to be changed to the locale that you want the bot to respond to. The current locale set on Composer does not get set on Emulator when we use the operation "Open in Emulator" from Composer.

[humak]

We tried your solution and it worked on Emulator. Thank you so much @srinaath !

We still couldn't reach the published bot from Azure Portal WebApp Chat.
Do you have any suggestion about how we can add this language parameter during/after publishing bot to Azure WebApp? Since these problems are connected and similar, I think we are also missing some point during publishing phase.

[dmvtech]

We still couldn't reach the published bot from Azure Portal WebApp Chat.
Do you have any suggestion about how we can add this language parameter during/after publishing bot to Azure WebApp? Since these problems are connected and similar, I think we are also missing some point during publishing phase.

Hi @humak Are you referring to Test in WebChat or full WebChat?

The locale of the browser should be the thing that is telling WebChat and the bot what locale should be used. For example, in Emulator, you can see what locale is being sent:

{
  "type": "conversationUpdate",
  "membersAdded": [
    {
      "id": "______________________________",
      "name": "Bot"
    },
    {
      "id": "______________________________",
      "name": "User"
    }
  ],
  "from": {
    "id": "______________________________",
    "name": "User",
    "role": "user"
  },
  "locale": "de-de",
  "serviceUrl": "http://localhost:64085"
}

Are you able to test with a browser using both English and Turkish locales?

[dmvtech]

Related: microsoft/BotFramework-Emulator#2268

[humak]

Hi @dmvtech , maybe I can explain better with this example.

1. I have a bot build in Bot Composer , the localization is Turkish. It works in local webchat.
   

2. It works in the Emulator when we changed the locale as you suggested:
   

3. Then we publish bot to Azure. And In the Azure Bot APP Test Webchat , the bot is not running.
   

We got this error when we publish the bot to Azure as locale tr-TR (Turkish.)

When the bot’s locale is en-us (english), it works.
The question is : Should we add a property to publishing profile when we are publishing in Turkish? We can send you the publishing profile as json.

[dmvtech]

@humak

When you publish, it will publish all locales that you have created/configured. Just to confirm; you did not remove en-US locale from the bot, correct?.

So, my assumption is that there is something wrong with the published bot, regardless of locale. The Test in WebChat and Azure portal are obviously running in English (I'm assuming en-US).

One thing you can do is use Ngrok and test your local running bot through the Test in WebChat tool. This will confirm that everything but the bot running in Azure (App Service) is working correctly.

Otherwise:

• Have you tried re-publishing?
• Gateway timeout usually means the bot was running long. Does it do anything at the beginning (of the conversation start), that might take a long time (API call, etc)?

[dmvtech]

Hi @humak. Have you tried any of the above? Any answers to the questions above?

[dmvtech]

Closing due to lack of response. Please comment with answers to above questions if you still need assistance.