Added support for Crashlytics didCrashOnPreviousExecution & setCustomKey #492
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
tsimbalar
reviewed
Aug 28, 2020
dpa99c
added a commit
that referenced
this pull request
Sep 10, 2020
…shOnPreviousExecution()`. Relates to PR #492.
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.
PR Type
PR Checklist
What is the purpose of this PR?
Closes #434.
Adds support for Firebase Crashlytics
didCrashOnPreviousExecution&setCustomKeyDoes this PR introduce a breaking change?
What testing has been done on the changes in the PR?
Tested on Android Phone and iOS iPad
What testing has been done on existing functionality?
Ensured push notifications and crashlytics logging continued to work.