-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add enableCrashlyticsCollection to Crashlytics #1718
Conversation
CI reported |
increment yarn caching version - eslint bug
Codecov Report
@@ Coverage Diff @@
## master #1718 +/- ##
==========================================
+ Coverage 76.1% 76.16% +0.06%
==========================================
Files 72 72
Lines 1837 1838 +1
==========================================
+ Hits 1398 1400 +2
+ Misses 439 438 -1 |
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #1718 +/- ##
==========================================
+ Coverage 76.1% 76.16% +0.06%
==========================================
Files 72 72
Lines 1837 1838 +1
==========================================
+ Hits 1398 1400 +2
+ Misses 439 438 -1 |
Thanks for this @timwangdev - looks great. Looks like the eslint issue is something to do with yarn caching on the ci, I've just pushed a commit on your branch to increment the cache version to wipe it, should be ok now - we'll see 👍 |
Well, I can't get the CI to |
Summary
Allow developer to manually initialize Crashlytics when disabled automatic initialization as described here. If the the module has already been initialized, this method should be a no-op according to Fabric docs.
This would be useful in cases like GDPR.
Checklist
Android
iOS
e2e
tests added or updated in /tests/e2e/*Test Plan
Pass e2e test.
Release Plan
[IOS] [ANDROID] [FEATURE] [CRASHLYTICS] - Add enableCrashlyticsCollection to Crashlytics
Think
react-native-firebase
is great? Please consider supporting the project with any of the below:React Native Firebase
andInvertase
on Twitter