Closed deodad closed 5 years ago
Transferring to botframework-services
because this is related to token renewal.
howdy @compulim, are you sure? I have no problems renewing the token... it's just that the webchat component isn't updating back into a connected state when the connectionStatus$ goes from Expired back to Online.
@adaddeo How are you obtaining the 'fresh token and streamurl' before step 4?
@EricDahlvang you'll need to call the DirectLine API reconnect endpoint.
Since your token is expired at this point you'll need to use a secret and thus will want to do this call server side.
I know this has been open for some time; however, did this ever get resolved @adaddeo ? Otherwise I will bring to the engineering team for feedback.
Closing due to lack of activity; feel free to create a new issue to resume the investigation.
Version 4.4.1 via NPM package
Unable to keep a conversation going after an ExpiredToken event followed by a call to
directline.reconnect
with a fresh token.When the connection status changes to ExpiredToken "unable to connect" appears but calling reconnect with the new token "unable to connect" stays.A strange piece of this is seeing the connectionStatus change to 5. It appears this is being done (intentionally or otherwise) by a saga in webchat.
To Reproduce
Steps to reproduce the behavior:
directline.reconnect
with a fresh token and streamUrlWe'd expect to see Webchat move back into "connecting" and then "connected" state and be able to continue the conversation.
[Bug]