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.
Description
Description
Details
Details
Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
apps/android/wikipedia | master | +2 -2 | Fix possible crash when fetching search results. |
Related Objects
Related Objects
- Mentioned Here
- T186933: 204 summary responses cause Android app to crash
Event Timeline
Comment Actions
Just to be explicit, the issue was probably not the non-200 error code but the empty payload.
Comment Actions
Change 414719 had a related patch set uploaded (by Dbrant; owner: Dbrant):
[apps/android/wikipedia@master] Fix possible crash when fetching search results.
Comment Actions
Change 414719 merged by jenkins-bot:
[apps/android/wikipedia@master] Fix possible crash when fetching search results.