[MS-1251] Make Simber.w throwable argument non-optional to avoid lumping all warnings together in Crashlytics#1467
Merged
Conversation
d468f76 to
cc50c9a
Compare
There was a problem hiding this comment.
Pull Request Overview
This PR addresses a long-standing issue where all warning logs in Crashlytics were grouped together into a single generic issue, making it difficult to monitor and triage different warning scenarios. The solution makes the Throwable parameter in Simber.w() non-optional, forcing callers to provide specific exceptions that will enable proper grouping in Crashlytics.
Key changes:
- Modified
Simber.w()to require a non-nullThrowableparameter - Updated all existing call sites to provide appropriate exception types with descriptive messages
- Simplified the internal logging logic by removing the null-handling branch
Reviewed Changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| infra/logging/src/main/java/com/simprints/infra/logging/Simber.kt | Made Throwable parameter non-optional and simplified internal logic to handle only non-null cases |
| infra/logging/src/test/java/com/simprints/infra/logging/writers/CrashlyticsLogWriterTest.kt | Removed test for deprecated null-Throwable behavior |
| infra/ui-base/src/main/java/com/simprints/infra/uibase/navigation/NavigationResultExt.kt | Added IllegalStateException for navigation failure warning |
| infra/matching/src/main/java/com/simprints/infra/matching/usecase/FingerprintMatcherUseCase.kt | Added IllegalArgumentException for missing SDK warning |
| infra/matching/src/main/java/com/simprints/infra/matching/usecase/FaceMatcherUseCase.kt | Added IllegalArgumentException for missing SDK warning |
| infra/event-sync/src/main/java/com/simprints/infra/eventsync/event/commcare/CommCareEventDataSource.kt | Added IllegalArgumentException for date parsing failure warning |
| feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/steps/FallbackToCommCareDataSourceIfNeededUseCase.kt | Added Exception for CommCare fallback scenario warning |
| infra/event-sync/src/test/java/com/simprints/infra/eventsync/event/commcare/CommCareEventDataSourceTest.kt | Updated test assertions to verify Throwable parameter is provided |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
luhmirin-s
approved these changes
Nov 19, 2025
meladRaouf
approved these changes
Nov 19, 2025
alexandr-simprints
approved these changes
Nov 20, 2025
cc50c9a to
76d5544
Compare
…ing all warnings together in Crashlytics
76d5544 to
3cf5521
Compare
|
This file contains hidden or 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
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.



JIRA ticket
Will be released in: 2026.1.0
Root cause analysis (for bugfixes only)
First known affected version: forever
Notable changes
Testing guidance
Additional work checklist