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

[📚] Crashlytics doesn't mention you need to enable analytics too. #8224

Closed
Crare opened this issue Jan 13, 2025 · 3 comments
Closed

[📚] Crashlytics doesn't mention you need to enable analytics too. #8224

Crare opened this issue Jan 13, 2025 · 3 comments
Labels
resolution: needs-repro This issue could not be reproduced or needs a repro provided. type: documentation

Comments

@Crare
Copy link

Crare commented Jan 13, 2025

Documentation Feedback

documentation page: https://rnfirebase.io/crashlytics/usage

There's no clear text stating that you need to actually also enable firebase analytics to make the crashlytics work. You can't see any data coming through without enabling firebase analytics.

This is mentioned on Firebase's documentation: https://firebase.google.com/docs/crashlytics/get-started?platform=android#before-you-begin

"Recommended: To automatically get breadcrumb logs to understand user actions leading up to a crash, non-fatal, or ANR event, you need to enable Google Analytics in your Firebase project.

If your existing Firebase project doesn't have Google Analytics enabled, you can enable Google Analytics from the Integrations tab of your settings > Project settings in the Firebase console.

If you're creating a new Firebase project, enable Google Analytics during the project creation workflow."

This issue probably gets unnoticed if you enable firebase analytics right from the start when you create the project in firebase.

@mikehardy
Copy link
Collaborator

🤔 but these two statements don't line up:

you need to actually also enable firebase analytics to make the crashlytics work

vs

Recommended: To automatically get breadcrumb logs to understand user actions leading up to a crash, non-fatal, or ANR event, you need to enable Google Analytics in your Firebase project.

"Need" vs "Recommended"

You do not need analytics to get crashlytics to work. You need crashlytics to get automatic breadcrumbs. That's different isn't it?

@mikehardy mikehardy added the Workflow: Waiting for User Response Blocked waiting for user response. label Jan 13, 2025
@Crare
Copy link
Author

Crare commented Jan 14, 2025

Well yes. it doesn't directly state that either. You can't see any data in Firebase though without activating analytics.

@mikehardy
Copy link
Collaborator

That's a strong assertion vs the docs so I tested it

https://github.com/mikehardy/rnfbdemo/tree/crashlytics-no-analytics

I set up a brand new firebase project and I specifically did not set up analytics during project setup. I added a new ios and android app and downloaded their config files.

Then I integrated app and crashlytics only, and added a native crash button and javascript crash button and loaded up the app.

It registered crash reports just fine in the console.

So I am unable to reproduce but I did try.

@mikehardy mikehardy added resolution: needs-repro This issue could not be reproduced or needs a repro provided. and removed Workflow: Waiting for User Response Blocked waiting for user response. Needs Attention labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: needs-repro This issue could not be reproduced or needs a repro provided. type: documentation
Projects
None yet
Development

No branches or pull requests

2 participants