Better error handling, logging for debugging purposes

j0x0j commented 2 years ago

We have been operating the app for a few weeks now and have enrolled more than 8000 farmers so far. There have been some interesting operation lessons learned from the field with real users.

One of the main issues that have taken a lot of our time is in debugging issues for particular users. It may be

[ ] Add current version number to enrollment _annotations when completing form. That way we know exactly which version the enroller used and its easier to diagnose a problem.
[x] Look into best practices for automated testing, maybe look at firebase tools or google play tools. Take a look at this page and others in the section. https://play.google.com/console/u/0/developers/7382467632883551284/app/4973515169482797485/pre-launch-report/overview
[x] Better logging, we need to be able to configure log level with a proper logging tool, not console.log
[x] Wherever there is a console.error we need to log it to a place where we can later inspect, right now any error logged in the app is unavailable to us. Please review best practices.
[ ] Take a look at Android Vitals
[ ] Look into uploading debug symbols, to better identify errors across the stack.
[ ] Implement automated runs of linter across all project files for better code quality.

tushali024 commented 2 years ago

@j0x0j

Add current version number to enrollment _annotations

in this should show the version number to the user or only store it in the backend for our reference?

tushali024 commented 2 years ago

Better logging, we need to be able to configure log level with a proper logging tool, not console.log

Can we use firebase analytics for log event?

tushali024 commented 2 years ago

Look into best practices for automated testing, maybe look at firebase tools or google play tools

Can we use Detox and jest for the automation test?

j0x0j commented 2 years ago

@j0x0j

Add current version number to enrollment _annotations

in this should show the version number to the user or only store it in the backend for our reference?

Store it in the _annotations dictionary, no need to show it to the user. The version number is showed in the menu on the home screen.

j0x0j commented 2 years ago

Better logging, we need to be able to configure log level with a proper logging tool, not console.log

Can we use firebase analytics for log event?

We can explore firebase analytics. One thing to keep in mind is that most enrollers work in low/no connectivity environments.

j0x0j commented 2 years ago

Look into best practices for automated testing, maybe look at firebase tools or google play tools

Can we use Detox and jest for the automation test?

You can propose tests using whatever tool you think is most appropriate. I know jest, don't know detox will look into it. But you can setup a prototype so we can review it together.

j0x0j commented 2 years ago

@tushali024 I created and invited you to a fresh firebase project

j0x0j commented 2 years ago

Where I would suggest a bit of caution is to depend heavily on firebase. I know their sdks change fast and sometimes its a hassle to stay up to date.

teamraincoat / agricat

Better error handling, logging for debugging purposes #77