-
Notifications
You must be signed in to change notification settings - Fork 134
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
RUMM-1796 Crash Reporting Logging #712
Conversation
2f1cfd6
to
2111e00
Compare
2111e00
to
3c6e614
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍. I left wording suggestions and change request on error: error
(see the comment).
Sources/Datadog/FeaturesIntegration/CrashReporting/CrashReportingWithRUMIntegration.swift
Outdated
Show resolved
Hide resolved
Sources/Datadog/FeaturesIntegration/CrashReporting/CrashReportingWithRUMIntegration.swift
Outdated
Show resolved
Hide resolved
Sources/DatadogCrashReporting/PLCrashReporterIntegration/CrashReport.swift
Outdated
Show resolved
Hide resolved
a75f971
to
05624b1
Compare
b9a8a80
to
8e9a82b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG 👍 , though what about this from RUMM-1796
:
INFO
log determining if the crash report is found after app launch, or if it's missing;
sendCrashReportIfFound()
seems a good place for it, no?
Problem was CR's `queue` leaking reference to global `userLogger` and running into threading race conditions on this being replaced by SDK's tear down logic in tests.
What and why?
Add logs to crash reporting.
How?
Inject user and internal logger to crash reporting plugin.
Review checklist