When non-Open311 issue submission fails user loses issue report

[barbeau]

Summary:

Reported by a user in Puget Sound:

It would be great if when I try to report an arrival time issue, that the app doesn't just say "Unable to send report" after I spent 3 minutes typing it up.

I can reproduce this using Puget Sound region, which means it's specific to non-Open311 issue submission (i.e., via the OBA server REST APIs).

Steps to reproduce:

1. Switch to Puget Sound region
2. View arrivals at a stop, tap on arrival time and choose "Report arrival time problem"
3. Turn on airplane mode
4. Fill out the form and tap the submission arrow in action bar

Expected behavior:

Communication will fail due to airplane mode, so an error message should be displayed to the user and it should stay on the same form so the user can re-submit again

Observed behavior:

Dialog says "Your issue has been successfully reported" with "Ok" button, but a Toast pops up that says "Unable to send the report. Try again?" and the user is returned to the arrival list screen after they tap "Ok", which means that they effectively lost the info they typed into the box.

Device and Android version:

App Version: 2.2.5
Model: Nexus 6P
OS Version: 8.1.0 / 27
Google Play Services App: 12.2.21 (440-188803320)
Google Play Services Library: 9452000
Region/API: Puget Sound (selected automatically)