Bug reporting code on iOS errors out

When trying to load older chat messages on the Keybase client on iOS on a spotty network connection I got the bug reporting interface. When I tried to report the bug relating to loading chat messages, sending the error report itself errored out with the following:

Error: API network error: Post https://api-0.core.keybaseapi.com/_/api/1.0/logdump/send.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Stack:
c@/var/containers/Bundle/Application/775E5AB8-0FE0-4019-8DF8-9BE099B9E9E2/Keybase.app/main.jsbundle:83:1599
/var/containers/Bundle/Application/775E5AB8-0FE0-4019-8DF8-9BE099B9E9E2/Keybase.app/main.jsbundle:83:966
value@/var/containers/Bundle/Application/775E5AB8-0FE0-4019-8DF8-9BE099B9E9E2/Keybase.app/main.jsbundle:85:3761
/var/containers/Bundle/Application/775E5AB8-0FE0-4019-8DF8-9BE099B9E9E2/Keybase.app/main.jsbundle:85:1285
value@/var/containers/Bundle/Application/775E5AB8-0FE0-4019-8DF8-9BE099B9E9E2/Keybase.app/main.jsbundle:85:2898
value@/var/containers/Bundle/Application/775E5AB8-0FE0-4019-8DF8-9BE099B9E9E2/Keybase.app/main.jsbundle:85:1255
value@[native code]

I get that the bug reporting interface isn't prime design real estate, but perhaps log this somewhere and report a bit more human-readable message to the user?

Start with the iOS bug-reporting flow and the logdump/send.json request described in the report; reproduce the failure on a spotty network connection. Done means the failure is logged somewhere useful and the user receives a human-readable error instead of the raw network and stack-trace message.