Discourse app gets unusable on remote server error

When a remote server where a Discourse instance is hosted has serious errors (ie 5xx codes) and only renders an error message, the view is pretty much stuck on that view because there are no navigation elements visible.

This happens at least on iOS. Restart of the app brings me back to the server overview.

Suggested behavior changes:

  1. The app should pre-fetch the first request to a server when a server is selected in the main menu before the web view is opened and display an error when a 5xx and maybe certain 4xx codes are returned before the web view is opened.
  2. The app should still detect such kinda errors and display a fallback message with the options to either reload the page or navigate back to the main menu of the app.
  3. The iOS app should support the swipe gesture from the left to navigate back to the main menu.
1 Like