Error screens show technical, unlocalizable messages #3113
Description
Steps to reproduce
- Run into an error screen for an RTCSessionError or an UnknownCallError:
Outcome
What did you expect?
User-facing error messages should be written in a manner that we can expect users with little technical knowledge to understand. Ideally they should also suggest some action to get things back on track (like "check your network connection" or "submit logs to help us track down the problem").
What happened instead?
These error screens present messages intended for developers without any context. (What is an RTCSession, or a MembershipManager, or a signal connection?) The messages cannot be localized into the user's language either.
Operating system
No response
Browser information
No response
URL for webapp
call.element.dev
Will you send logs?
No