verbose network error details

[draeath]

Pitch

Currently, if something goes wrong, Tusky simply reports "An error occurred." This is insufficient for any sort of troubleshooting, especially for an application that utilizes APIs.

Additionally, even logcat seems to not contain any details about the problem.

It's fine to hide this sort of issue normally, but there should be a means to capture the error details so that they can be passed along.

Motivation

My instance admin has several users, myself included, experiencing some sort of error accessing the "trending posts" and a few other pages after upgrading their instance. We are unable to provide any sort of useful client-side troubleshooting information due to this.

[connyduck]

The quickest way to see the problem would be running a debuggable Tusky build and checking logcat.
But yes, there should be a way to get the actual error in the regular app as well.

[draeath]

If it's helpful in an illustrative manner, we found that the issue ended up being reproducible in the web interface as a 500 response for /api/v1/trends/statuses

Root cause happened to be an upstream Mastodon bug: mastodon/mastodon#33555