Webchat with DirectLine App Service Extension not rendering the SuggestedActions and activities onMembersAdded

[saravana-sk]

Is it an issue related to Adaptive Cards?

No

Is this an accessibility issue?

No

What version of Web Chat are you using?

Latest production

Which distribution are you using Web Chat from?

Bundle (webchat.js)

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

Browser: Chrome (latest)

Which area does this issue affect?

Suggested action

What is the public URL for the website?

No response

Please describe the bug

I configured the azure bot with App Service. While initiating the bot in web app using webchat with directline app service extension, the initial activities received from bot service in websocket is not rendering properly.

If I use directline secret instead of token, it is rendering properly.

Do you see any errors in console log?

No response

How to reproduce the issue?

1. Create a simple bot using using nodejs, that sends some plain message onMembersAdded and some suggestedActions
2. Initialize directLine with token in web app and trigger renderWebChat method
3. See whether the plain text activity and suggested actions are rendering in the webchat container

What do you expect?

It should render the message and suggested actions whenever user connects with the bot.

What actually happened?

The initial message and suggested actions are not rendering while using token for DirectLine. whereas it works while using the DirectLine Secret.

Do you have any screenshots or recordings to repro the issue?

This is on using token for directline:

This is on using secret for directline:

Adaptive Card JSON

No response

Additional context

No response

[saravana-sk]

is there any update on this issue?

[stevkan]

@saravana-sk - Thank you for your patience. A few questions:

• Have you observed any reported errors in the browser's dev console when using the token?
• Could you try using the generated token in a non-App Service Extension Web Chat instance to verify there isn't an issue with the token? For example, in the Getting Started sample? To achieve this:
  • Console log the token value when attempting to run the ASE site.
  • Copy the value and paste it into the sample so that it is hard-coded, like so: createDirectLine({ token: "Eyj....7sd" })
  • Open the sample in a browser and test for a response.
• Are you able to provide a copy of your code or a minimum reproducible example that I may test against?
• Which version of Node are you running?
• Which version of Chrome are you using? Have you tried in Edge or any other browser?

[stevkan]

Closing due to inactivity.