Add Sentry & Remove Firebase{Crashlytics, Analytics} #854
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Required making more generic the messaging around the privacy toggles. It is worth noting that the previous Crash Reporting preference is lost since it was using Firebase directly to store it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required making more generic the messaging around the privacy toggles. It is worth noting that the previous Crash Reporting preference is lost since it was using Firebase directly to store it.
Features like automatic/logging-based breadcrumbs, error logging and messaging are controlled by the analytics key. The crash reporting feature is controlled by crash reporting.
These require being able to log into our Sentry account:
Example non-fatal (with all the logging)
Example non-fatal (with no logging)