Fix: add logging to empty catch blocks in ReportContext#138
Open
Xenon010101 wants to merge 1 commit into
Open
Conversation
Closes madanrajsagar#77 Added console.warn logging to two empty catch blocks in ReportContext (hydration from storage and persistence to storage) so that silent failures are observable during development and debugging. Signed-off-by: Xenon010101 <xenon010101@users.noreply.github.com>
Author
|
Hi @madanrajsagar, just checking if there's anything blocking this from merging. Happy to make changes if needed. |
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
1 participant
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.
Closes #77
Root cause: Two empty catch blocks in ReportContext (lines 19 and 37) silently swallowed errors during AsyncStorage hydration and persistence, making it impossible to debug storage failures.
Fix: Added console.warn logging with the error object to both catch blocks so that storage failures are observable during development and debugging.