PAINTROID-815 Crash at App Start - #1367
Open
harissabil wants to merge 1 commit into
Open
harissabil wants to merge 1 commit into
harissabil wants to merge 1 commit into
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
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.
Summary
Release builds crash on launch / app start after process death. Reproduce with Developer Options > "Don't keep activities", open the app, press Home, reopen.
FragmentManager restores fragments reflectively through their no-arg constructor. R8 cannot see that call, so it removes the constructor. Confirmed with apkanalyzer that the constructor is missing from the release build.
R8 full mode became the default with the AGP 8 upgrade. release-2.13.0 built with AGP 7.2.1, does not crash.
a.ehas not been retraced against the release mapping, so the exact fragment is not confirmed.PaintroidApplicationFragmentis the most likely. The fix is a keep rule inapp/proguard-rules.pro, using-keepclassmembersrather than-keepso class names stay obfuscated.Tested with a minified release build; the rule no longer crashes with "Don't keep activities" option enabled.
Your checklist for this pull request
Please review the contributing guidelines and wiki pages of this repository.