echo-bot | An example Discord bot | Bot library

This error message always means you have not awaited something that should be awaited. You can see the following line in your constructor:

By reading the manual carefully and doing the following steps I achieved to connect the bot with the Emulator.

Configure the emulator for authentication

If a bot requires authentication, displaying a login dialog, you must configure the emulator as shown below.

Using sign-in verification code

1. Start the emulator.
2. In the emulator, click the gear icon in the bottom left, or the Emulator Settings tab in the upper right.
3. Check the box by Use a sign-in verification code for OAuthCards.
4. Check the box by Bypass ngrok for local address
5. Click the Save button.

https://docs.microsoft.com/en-us/azure/bot-service/bot-service-debug-emulator?view=azure-bot-service-4.0&tabs=csharp#configure-the-emulator-for-authentication

I will answer this question myself as i was able to work around the error. It does bring up certain security issues but resolves the invalid access issue.

As per the documentation Bot Registration

In the section Supports account types, you must choose one of the 2 multi-tenant types that is: Accounts in any organizational directory (Any Azure AD - Multitenant) or Accounts in any organizational directory (Any Azure AD - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox, Outlook.com), when creating the app, otherwise the bot will not work.

Making this change to the App registration resolved the error and the service is working fine. Thanks to everyone that tried to chip in with their inputs.

Can you please try:

The Neural voice exact name is Microsoft Server Speech Text to Speech Voice (en-US, JessaNeural). But the main thing is that you wanted to use a speaking style, using mstts:express-as.

The thing is that you forgot to add the block declaring mstts namespace in the xml (xmlns:mstts='https://www.w3.org/2001/mstts'):

I found this github telebot repo from yukuku with the setup of a telegram bot on App Engine and the webhook implementation using python. As mentioned before you may want to use App Engine in order to implement your bot with many functions on the same main.py file.

I just tried and it's working for me.

Short answer: yes.

Long answer: Emulator uses WebChat, which uses Directline-JS. So, when you're using the Emulator, you're using the WebChat channel.

However, Emulator, just added the Bot Inspector to recent releases. This allows you to attach to conversations on other channels like Skype or Facebook and view the conversation, live, through the emulator. See the link above for setup instructions, but the gist of it is:

1. Add the inspector middleware to your bot
2. Use ngrok or an Azure Service Bus Relay to connect Bot Inspector to your Hosted Bot
3. Start a chat with your bot in a channel, and type the code Bot Inspector gives you (/INSPECT attach )
4. Your conversation is then attached to Emulator and you can view all traffic between your bot and the user (you) in that channel

Note: Bot Inspector is super new. There's still some kinks to work out and instructions are a little sparse, but it works well, otherwise. You can view samples that already have the Inspector Middleware code here:

• JS/Node
• C#

Note: Bot Inspector Mode is different from the Inspector Pane

By default privacy mode is enabled for Telegram bots.

A bot running in privacy mode will not receive all messages that people send to the group. Instead, it will only receive:

Messages that start with a slash ‘/’ (see Commands above)

Replies to the bot's own messages

Service messages (people added or removed from the group, etc.)

Messages from channels where it's a member

You could disable privacy mode for your bot through BotFather.

A new EchoDialog will be created each time the delegate is executed, which will be an implementation detail of SendAsync. Basically, you're passing a method definition to SendAsync and it will call that method one or more times. Each time it calls delegate, the code on the right side of the => will be executed.