[Android] Revert Native processing parsing #502
Merged
Conversation
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
murki
approved these changes
Jul 16, 2025
FranAguilera
force-pushed
the
franjam/temporary-revert-native-crash-processing
branch
from
9727014 to
40a20a1
Compare
📦 APK Size Report
|
FranAguilera
deleted the
franjam/temporary-revert-native-crash-processing
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Reverting processing of native crashes given potential impact on app launch if
Capture.Logger.startis called on the main threadThis will be applied again once BIT-5823 is completed
Early Results investigation
Verification
Trigger native crash on sample app, capture start time for fatal issue reporting should remain minimal
https://timeline.bitdrift.dev/session/5ace80d4-9ba0-4730-ae6e-7171e265fbac?utm_source=sdk&pages=1&utilization=0&expanded=6175029687503967458