-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More descriptive error messages than 'couldn't send' #1163
Comments
@SarahSexton are you referring to this message under the failed message's chat bubble? Or is it a message in the log panel that you are referring to? If you send a message in the v4 Emulator, you should be able to click on the error code in the log and see the HTTP response in the inspector: If it's the former, we should move this over to WebChat. |
I am referring to the former: the message under the failed message's chat bubble. "Couldn't send." Sorry for the ambiguity. |
No worries, I will move this over to the WebChat repository then because that UI is embedded in the WebChat control and out of the control of the Emulator. |
@compulim Tagging because this would need to be a Webchat change. |
Wouldn't the message in the log panel provide sufficient information about the error? The message under the chat bubble is not meant to be comprehensive and probably should not be due to the limited screen real estate. |
Hello! This is going to be addressed in the Offline UI set of stories in the WebChat project here |
When I use the Emulator, instead of the error message simply saying "couldn't send," it should be a lot more descriptive. Describe in more detail, such as, "Failed to establish a TCP IP connection. Did you remember to start your emulator?"
The text was updated successfully, but these errors were encountered: