-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Proposal Crashlytics/Firebase logging #2726
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
Conversation
(cherry picked from commit 429e2dc)
|
For Countly it can also very easy be done. |
|
I close it, till you decide to go with it |
|
@jesmrec Open general issue for crash/debug solution for better tracking? |
|
For me it is a good idea to move the idea of @hannesa2. I will create an issue pointing such ideas. |
|
I only want to show you the crashes of 3 known (with rare usage) users of my personal app the last 30 days |
|
We are aware about these errors, and working in fixing them. We have this issue to work on this topic, take reviews etc... the current PR is really interesting, but it is u2u to keep it open or close. Thanks for your engagement. |
|
If someone reopen it, I would update the PR with a more recent way of initialization, because Google shutdown standalone Crashlytics. Now it's an sub-area of Firebase |



(cherry picked from commit 429e2dc)
This is a proposal of #2694 (comment)
The discussion yes/no is your task.