microsoft / microsoft/BotFramework-WebChat
Webchat connection gets stuck when iOS App container comes back from background
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
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?
NPM
Which hosting environment does this issue primarily affect?
Web apps
Which browsers and platforms do the issue happened?
Platform: iOS/iPadOS
Which area does this issue affect?
Protocol or service
What is the public URL for the website?
No response
Please describe the bug
Webchat is connected through ASEDL to a custom bot, Websocket in the mix. Hosting is done on iOS WKWebKit.
App is running the webchat, app gets put on background, you start camera (or anything), 30 seconds later you go back to the app, connection will not be established. Send button is disabled
When webchat gets into foreground again, there'll be two new logs:
- WEB_CHAT/SET_NOTIFICATION (reconnecting)
- DIRECT_LINE/UPDATE_CONNECTION_STATUS
Connection status will be stucked at 1, connecting.
We logged Webbrowser WebSocket too:
-
before leaving the window we would have 1 websocket in a readyState = 1 (OPEN) state
-
returning back we see two websockets: 1) in readyState = 1 (OPEN) state, 2) in readyState = 3 (CLOSED) state
CC: @miketrexler
Do you see any errors in console log?
No response
How to reproduce the issue?
- App is running the webchat,
- App gets put on background,
- Start camera (or anything), 30 seconds later you go back to the app, connection will not be established. Send button is disabled
- Click on ...
- Type "..." in the send box
What do you expect?
Connection is re-established, conversation can be continued, send message is enabled
What actually happened?
Connection is not being re-established, send button is disabled, user is presented with warning around inability to connection (couple of different messages, second after 2 minutes from the first warning)
Do you have any screenshots or recordings to repro the issue?
Yes, can provide privately
Adaptive Card JSON
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.