Page MenuHomePhabricator

Ensure that all network handlers can gracefully handle HTTP Success codes other than 200.
Closed, ResolvedPublic3 Estimated Story Points

Description

A recent task (T186933) has revealed a potential source of crashes, whereby a network response comes back as successful (i.e. HTTP 2xx status) but is not 200, meaning that the response body doesn't contain the structure that we expect. We need to ensure that the app handles these types of codes correctly and gracefully, and certainly doesn't crash.

Event Timeline

Just to be explicit, the issue was probably not the non-200 error code but the empty payload.

Change 414719 had a related patch set uploaded (by Dbrant; owner: Dbrant):
[apps/android/wikipedia@master] Fix possible crash when fetching search results.

https://gerrit.wikimedia.org/r/414719

Charlotte set the point value for this task to 3.Feb 26 2018, 5:41 PM

Change 414719 merged by jenkins-bot:
[apps/android/wikipedia@master] Fix possible crash when fetching search results.

https://gerrit.wikimedia.org/r/414719

Charlotte triaged this task as Medium priority.