Improve ability to debug Gateway issues in production #172
Description
Is your feature request related to a problem? Please describe.
Historically, there have been behaviours and issues in Gateway that is hard to debug in production and it could be affecting projects.
There are many variables to consider: Phone model, Android version, Internet connection, etc.
The current log screen has a very short history list and logcat not always is the best option for debugging since some issues are reported to only happen when the phone isn't connected to the computer.
Describe the solution you'd like
Do some research:
- See if Android has something to improve the debug experience for production environment.
- Check the mobile dev community and see what other apps do to mitigate this situation.
We need:
- Detailed logs and more log captures overtime.
- Phone information: brand, model, current memory (running out?), current storage (running out?).
- If possible environment information: was the internet signal okay?
Describe alternatives you've considered
- Keep a file in the phone with all that information and it will clear itself periodically (every 2 or 4 months).
- If the phone's space is a concern, then store the information in the cloud (medic's couchDB?) and maybe flag when there's an exception. But then it needs to keep the info in cache, if there's not internet and then update when it gets signal again (?)