-
Notifications
You must be signed in to change notification settings - Fork 53
[PM-11910] Improve Crashlytics logs #1011
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
Conversation
…ype and customizing user info for CustomNSError on Error with associated values.
No New Or Fixed Issues Found |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1011 +/- ##
==========================================
- Coverage 89.10% 89.06% -0.04%
==========================================
Files 657 660 +3
Lines 41317 41390 +73
==========================================
+ Hits 36814 36866 +52
- Misses 4503 4524 +21 ☔ View full report in Codecov by Sentry. |
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, just a few linting warnings that I noticed.
BitwardenShared/Core/Platform/Services/API/Errors/ServerError.swift
Outdated
Show resolved
Hide resolved
BitwardenShared/Core/Platform/Services/EnvironmentService.swift
Outdated
Show resolved
Hide resolved
BitwardenShared/Core/Platform/Services/EnvironmentServiceTests.swift
Outdated
Show resolved
Hide resolved
…swift Co-authored-by: Matt Czech <matt@livefront.com>
Co-authored-by: Matt Czech <matt@livefront.com>
….swift Co-authored-by: Matt Czech <matt@livefront.com>
Co-authored-by: Matt Czech <matt@livefront.com>
🎟️ Tracking
PM-11910
📔 Objective
Improve Crashlytics error reports so we can identify issues causes easier.
UserId
to the reports.Region type
to the reports, i.e.US
,EU
orSelf-Hosted
(no specific URL configuration is logged)CustomNSError
on someError
with associated values so that additional info can be set in theerrorUserInfo
to be sent to Crashlytics and we have a better understanding on the context of such errors.⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes