Remove minifyEnabled
flag for Android for a readable Crashlytics stack trace
#946
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.
We had the problem that our stack trace was not readable (see #835). This is a huge problem for us because we want to detect errors in our beta and alpha versions and fix them. Without the stack trace it's super hard to fix them.
I'm pretty sure that the
minifyEnabled
flag obfuscates the stack trace. I would value the stack trace much higher than a bit smaller APK file. But I also made the test:sz build android --output-type apk
(withminifyEnabled
): 54.0 MBfvm flutter clean && sz build android --output-type apk
(withoutminifyEnabled
): 54.0 MBFixes #835