In many different spots in the app, the server is returning 400's (with high consistency beginning late last year), and it's not clear why.

Try to understand or reproduce the error to understand the cause, and if that fails to occur, at the very least:

1. Try to reproduce the response so we can understand what kind of client/server interaction failure is occurring.
2. Work with the server team to search the Bugsnag report (linked below) for anything useful to be gleaned from the log data.
3. If there's no quick solution to finding the issue this way (e.g if we can't see enough info in Logly), update the build to collect and return all the JSON Problem Documents for any of these 400's (only the 400's for this ticket, but can be a general rule for other error types - later), and return them back to us (either back through bugsnag, or some other equivalent means that we can quickly analyze them.)

The error surfaces in earnest near the end of November:

[https://app.bugsnag.com/nypl-1/android-simplified/timeline?filters[error.status][0][type]=eq&filters[error.status][0][value]=open&filters[search][0][type]=eq&filters[search][0][value]=400&filters[event.since][0]=2018-11-15T17%3A36%3A04.966Z&filters[event.before][0]=2019-01-17T16%3A43%3A45.682Z]