Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error handling, logging for debugging purposes #77

Open
3 of 7 tasks
j0x0j opened this issue May 6, 2022 · 8 comments
Open
3 of 7 tasks

Better error handling, logging for debugging purposes #77

j0x0j opened this issue May 6, 2022 · 8 comments
Labels
enhancement New feature or request

Comments

@j0x0j
Copy link
Member

j0x0j commented May 6, 2022

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.
  • 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
  • Better logging, we need to be able to configure log level with a proper logging tool, not console.log
  • 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. Screen Shot 2022-05-06 at 12 43 48 AM
  • Implement automated runs of linter across all project files for better code quality.
@j0x0j j0x0j added the enhancement New feature or request label May 6, 2022
@tushali024
Copy link
Contributor

@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
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Member Author

j0x0j commented May 7, 2022

@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
Copy link
Member Author

j0x0j commented May 7, 2022

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
Copy link
Member Author

j0x0j commented May 7, 2022

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
Copy link
Member Author

j0x0j commented May 7, 2022

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

@j0x0j
Copy link
Member Author

j0x0j commented May 7, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants