Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proguard rules for :gravatar module #359

Merged
merged 2 commits into from
Oct 8, 2024
Merged

Conversation

AdamGrzybkowski
Copy link
Contributor

Closes #345

Description

This PR provides pro guard rules that will be shipped with our SDK so that our code won't crash if isMinifyEnabled in third-party app is enabled.

Testing Steps

Run the demo app with the release build type and try to test each tab. Ideally, test trunk first to confirm there was an issue (crash).

isMinifyEnabled = false
isMinifyEnabled = true
isShrinkResources = true
signingConfig = signingConfigs.findByName("debug")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure we want it like that, but it's nice for testing and we don't use it for anything else right now.

@wpmobilebot
Copy link
Collaborator

wpmobilebot commented Oct 7, 2024

📲 You can test the changes from this Pull Request in Gravatar Demo by scanning the QR code below to install the corresponding build.
App Name Gravatar Demo
Commitfb30f9e
Direct Downloadgravatar-demo-prototype-build-pr359-fb30f9e.apk

Copy link
Contributor

@hamorillo hamorillo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works as described! 🚀

💡Not directly related with this PR. For the demo-app prototype we are using the debug buildType. Can it make sense to use the release one in order to test the library with the proguard rules?

@AdamGrzybkowski
Copy link
Contributor Author

Not directly related with this PR. For the demo-app prototype we are using the debug buildType. Can it make sense to use the release one in order to test the library with the proguard rules?

Yeah we should do it. #361

@AdamGrzybkowski AdamGrzybkowski merged commit 86f1ba9 into trunk Oct 8, 2024
16 checks passed
@AdamGrzybkowski AdamGrzybkowski deleted the adam/345_rules branch October 8, 2024 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement :gravatar Gravatar core module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Test the SDK against code obfuscation
3 participants