Skip to content

docs: Add Android release build troubleshooting section#116

Closed
BSchindeleAnother wants to merge 1 commit intosk3llo:masterfrom
BSchindeleAnother:docs/android-release-build-troubleshooting
Closed

docs: Add Android release build troubleshooting section#116
BSchindeleAnother wants to merge 1 commit intosk3llo:masterfrom
BSchindeleAnother:docs/android-release-build-troubleshooting

Conversation

@BSchindeleAnother
Copy link

This PR adds up documentation to set up the necessary proguard exception for release builds to work on android, as proposed in #76.

Added troubleshooting guide for common android release build issues due to missing proguard rules.
@niclasEX
Copy link

niclasEX commented Jan 5, 2026

@BSchindeleAnother
What are your thoughts on #133 #129
Is there a reason not to do it with consumer rules?

@niclasEX
Copy link

niclasEX commented Jan 5, 2026

If this is to be added to the documentation it might make sense to also include documentation for kotlin:

buildTypes {
    release {
        {... existing lines ...}
        isMinifyEnabled = true
        isShrinkResources = true
        proguardFiles(
            getDefaultProguardFile("proguard-android-optimize.txt"),
            "proguard-rules.pro"
        )
    }
}

@sk3llo
Copy link
Owner

sk3llo commented Feb 8, 2026

@BSchindeleAnother thank you for this PR, but there is a specific section in Wiki with the common bugfixes that files this case

@sk3llo sk3llo closed this Feb 8, 2026
@niclasEX
Copy link

Does it not make sense to include the ProGuard rules in this project. Or is there any drawback when doing this?
The current workflow is: Depend on this package, run into a bug, find the wiki, apply the fix. This can take quite a lot of time as the error only occurs in release builds and only on android. And the error output is not very descriptive, so it might take quite some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants