🔪 Allow for the build to automatically strip debug symbols from .so files #18
Conversation
This file contains 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
KYovchevski
force-pushed
the
strip-debug-symbols
branch
from
d002daa to
2df1495
Compare
Jasper-Bekkers
approved these changes
Oct 30, 2024
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.
For the Play Store publishing pipeline to be able to also upload debug information files to Sentry, we need to build the android app with Debug symbols. However, we also don't want to upload the debug symbols to the play store.
This is the solution to this problem: add an additional optional step that will copy the .so file with the debug information to a separate directory where it can be accessed by sentry-cli, while the original gets stripped of debug symbols in preparation to getting uploaded to the play store.