There are many bug reports after the new iOS release, where the app fails at some stage with “an error has occured”. It’s hard to pin point, if the issue is the reverse proxy, a server side bug, a data inconsistency, what ever. To help users (and yourself when you get confronted with such bug reports) narrow down what the actual problem is, it would be very helpful if the error message could be expanded to more technical details. Knowing that some field cannot be unmarshalled or some encoding is wrong, or whatever else could help tremendously in fixing the actual root cause, even (or especially) if it’s outside of the app itself. Having access to log files (maybe via an “export logs” button in the advanced settings?) might help as well (at least if the app works to the point where you can get to this settings page).