You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using DLASE when sending messages from WebChat (preferably file attachments), the BF-Connector TransportHandler.ListenAsync method functionality that reads from NamedPipes is executed after the ActivityHandler.OnMessageActivityAsync event from the bot.
So when sending a file attachment, the MemoryStream information comes empty.
This issue happens randomly, since it could be an asynchronous issue.
To Reproduce
Steps to reproduce the behavior:
Configure NamedPipe in an Echo bot, and use a DLASE WebChat client.
Add a breakpoint to the TransportHandler.ListenAsync (line 50).
Add a breakpoint to the bot's ActivityHandler.OnMessageActivityAsync.
Send a file attachment over WebChat.
The 3rd step (breakpoint) should be hit first, instead of the 2nd step.
Expected behavior
The file information (MemoryStream) inside the activity's attachment should come with buffer data.
Screenshots
The text was updated successfully, but these errors were encountered:
Version
main (4.22.9)
Describe the bug
Using DLASE when sending messages from WebChat (preferably file attachments), the BF-Connector
TransportHandler.ListenAsync
method functionality that reads from NamedPipes is executed after theActivityHandler.OnMessageActivityAsync
event from the bot.So when sending a file attachment, the
MemoryStream
information comes empty.This issue happens randomly, since it could be an asynchronous issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The file information (MemoryStream) inside the activity's attachment should come with buffer data.
Screenshots
The text was updated successfully, but these errors were encountered: