Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Crash with forceCrash not reported

See original GitHub issue

Hey @long1eu I just notice that there still an issue when forceCrash is true, I don’t receive anything on Crashlytics for those crash 😕

Issue Analytics

State:
Created 5 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

long1eucommented, Jan 10, 2019

Sure.

În joi, 10 ian. 2019, 14:04 Jaumard <notifications@github.com a scris:

Don’t know if you’re using Firebase instead of Crashlytics but if it’s the case, can you update the Readme to have the right setup steps for it ? Because there some issues about setup firebase instead of fabric with this plugin…

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kiwi-bop/flutter_crashlytics/issues/49#issuecomment-453073052, or mute the thread https://github.com/notifications/unsubscribe-auth/AI2nVltFzpFOu9DA55_-Oky6SWNr6WxSks5vByxkgaJpZM4Z3UHr .

0reactions

jaumardcommented, Jan 10, 2019

Don’t know if you’re using Firebase instead of Crashlytics but if it’s the case, can you update the Readme to have the right setup steps for it ? Because there some issues about setup firebase instead of fabric with this plugin…