| Summary: | NeoChat doesn't bubble libquotient auth errors up to the user, so it can be hard to troubleshoot basic issues | ||
|---|---|---|---|
| Product: | [Applications] NeoChat | Reporter: | Nate Graham <nate> |
| Component: | General | Assignee: | Tobias Fella <fella> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | carl, josh, justin |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | What app showed vs what console log showed | ||
*** Bug 510284 has been marked as a duplicate of this bug. *** |
Created attachment 181359 [details] What app showed vs what console log showed Today I ran into an issue where there's (apparently) some kind of auth token issue. This manifests as NeoChat logging me in without issue, but displaying a loading progress bar forever when trying to display the contents of every room. Looking in the console log, I found evidence of auth issues. But the UI never reported any of this. If I didn't know how to look at the log, I'd be pretty stuck, and have no idea how to proceed. See attached screenshot.