Skip to content

Conversation

@hannesa2
Copy link
Contributor

@hannesa2 hannesa2 commented Nov 15, 2019

(cherry picked from commit 429e2dc)

This is a proposal of #2694 (comment)

The discussion yes/no is your task.

image

(cherry picked from commit 429e2dc)
@hannesa2
Copy link
Contributor Author

For Countly it can also very easy be done.
Please see this comment #2694 (comment)

@hannesa2
Copy link
Contributor Author

I close it, till you decide to go with it

@hannesa2 hannesa2 closed this Nov 18, 2019
@michaelstingl
Copy link
Contributor

@jesmrec Open general issue for crash/debug solution for better tracking?

@hannesa2 hannesa2 deleted the ProposalCrashlyticLogging branch November 19, 2019 05:36
@jesmrec
Copy link
Collaborator

jesmrec commented Nov 19, 2019

For me it is a good idea to move the idea of @hannesa2. I will create an issue pointing such ideas.

@hannesa2
Copy link
Contributor Author

I only want to show you the crashes of 3 known (with rare usage) users of my personal app the last 30 days
I guess, if you have this too, you will see a lot of errors
@michaelstingl

image

@jesmrec
Copy link
Collaborator

jesmrec commented Jun 25, 2020

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.

@hannesa2
Copy link
Contributor Author

hannesa2 commented Jul 14, 2020

I can't reopen it

image

@hannesa2
Copy link
Contributor Author

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

@michaelstingl
Copy link
Contributor

Can't re-open too, sorry

CleanShot 2020-07-14 at 09 49 17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants