Incident offline storage implemented; need to test

[williamvanderkamp]

I have implemented offline storage and delayed online sending of incidents on the app.

But I haven't really tested it yet, and there are likely issues.

Any volunteers?

[add118]

I haven't been testing directly but I've been dealing with confusing repercussions of incident storage.

Say I have 3 stored incidents, Upon pressing "Create Incident" 1 saved incident attempts to send to the server. If it makes it I get "Incident successfully sent" which is great, but a bit confusing for a few seconds. Maybe this toast shouldn't be sent?

I also think that all stored incidents should send upon pressing the button if they have the opportunity, not just one at a time. If 3 are stored I have to press "Create Incident" 3 times to send them all.

[williamvanderkamp]

They should all be sending automatically, regardless of create incident. In
fact the thread for sending stored incidents starts as soon as the app
opens.
On Apr 7, 2015 2:18 PM, "add118" notifications@github.com wrote:

I haven't been testing directly but I've been dealing with confusing
repercussions of incident storage.

Say I have 3 stored incidents, Upon pressing "Create Incident" 1 saved
incident attempts to send to the server. If it makes it I get "Incident
successfully sent" which is great, but a bit confusing for a few seconds.
Maybe this toast shouldn't be sent?

I also think that all stored incidents should send upon pressing the
button if they have the opportunity, not just one at a time. If 3 are
stored I have to press "Create Incident" 3 times to send them all.

—
Reply to this email directly or view it on GitHub
#53 (comment).