3 separate new parts of the app need thorough testing and debugging #59
Description
- Offline storage and opportunistic sending of completed incidents.
- Querying of channel identifiers from the server, selection of a particular identifier on the UI, and starting of IncidentActivity based upon the chosen channel.
- Querying of all subscribed channels from the server, storage of those subscribed channels, and populating the incident spec of IncidentActivity based upon those subscribed channels.
None of these have ever been successfully tested, even in a best-case scenario. I don't know of any problems with the implementations of these, but I'm sure they are lurking under the surface.
1 and 3 both involve File IO on the app. We know File IO works, because it has been successfully used to pause and resume incidents that are currently being worked on.