[BIT-9016] Proposal: include all possible information in report#181
Merged
ArielDemarco merged 4 commits intoJul 13, 2026
Conversation
kattrali
reviewed
Jul 13, 2026
kattrali
left a comment
kattrali
left a comment
Contributor
There was a problem hiding this comment.
looks good to me so far
kattrali
approved these changes
Jul 13, 2026
FranAguilera
approved these changes
Jul 13, 2026
Contributor
Author
|
For now, we have not defined the optimal approach for Android, including which errors or crashes we should capture, what the structure of each one should look like, and what information we want to collect, display, or use. Since iOS is the more urgent platform, we're merging the changes with iOS support only for now. We can later define the Android side of things (cc @FranAguilera) |
ArielDemarco
deleted the
ademarco/bit-9016-define-crash-fbs-with-all-the-data-related-to-a-crash
branch
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Overview
The idea is to keep as much raw crash data as possible instead of forcing the SDK to decide on a final interpretation too early. This is important because different reporters can provide different information about the same crash, and we should have/expose that data. Having all of it gives the backend more flexibility later for grouping, display, workflows, and future logic changes without needing SDK changes again.