-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
[Enhancement] Add Logs for Exception/Error/ Crash in the App #427
Comments
Thank you for your contribution to Talawa, please read our contributing guide |
hey @StrangeNoob you should join slack channel first because i have already asked for permission regarding this. The code is in code freeze so no new enhancement. So i was holding the same issue |
please join slack channel first |
I am in Slack and I have talked about this @Sagar2366 a couple of minutes about this error. I am not sure what you and @Sagar2366 have discussed. But I didn't anything about this talawa channel. |
As the talawa api is in code freeze there is nothing we can do in it |
I know @yasharth291 about the code freeze. I will be working on it after the code freeze. It's just an enhancement. |
@StrangeNoob please update issue description by following issue template and starting working on this issue. |
Issue Description:
Add Logs for the Exception/Error/Crash in the App. As in the production, we won't be able to have every device to debug. It would be easy to keep log of these errors, exception and rectify in the following build. Having a scheduler to update the logs in our server for the last 24-36 hours will be helpful for the developers to know the bugs and its seriousness.
Issue Severity:
It's an Enhancement.
Environment Details:
It can be implemented in both Android and IOS App.
Does this issue need immediate attention?
No, It's not that important but a good to have feature in the next updates.
Are you willing to work on this issue:
Sure why not.
Other information:
It would be better to implement f_logs and Firebase Crashlytics.
I would suggest implementing cron for scheduling purpose.
The text was updated successfully, but these errors were encountered: