[Android] [Fatal Issue] Support nested stack trace#464
Merged
FranAguilera merged 1 commit intomainfrom Jun 26, 2025
Merged
Conversation
FranAguilera
force-pushed
the
franjam/bit-5699-support-chained-exceptions
branch
from
7eb1807 to
790c120
Compare
FranAguilera
force-pushed
the
franjam/bit-5699-support-chained-exceptions
branch
from
790c120 to
a77e0f0
Compare
📦 APK Size Report
|
kattrali
approved these changes
Jun 26, 2025
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.
2 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.
What
Resolves BIT-5699
We weren't handling nested stacktraces for BuiltIn mode.
NOTE: As a follow up will update issues frontend to apply same rendering logic for chained exception as displayed in timeline
Verification
Chained
Session
Steps:
Regular
Session
Steps: