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

[android] Update gradle plugun and androidx deps #8141

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

biodranik
Copy link
Member

No description provided.

@biodranik biodranik requested review from vng and rtsisyk May 11, 2024 13:08
@@ -22,7 +22,7 @@ buildscript {
googleFirebaseServicesDefault

dependencies {
classpath 'com.android.tools.build:gradle:8.3.2'
classpath 'com.android.tools.build:gradle:8.4.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd rather wait until 8.4.1 is out.. There is no need to rush, its better to wait until newly introduced bugs are found and fixed.

Also 8.4 introduces new minification changes which should be tested thoroughly https://developer.android.com/build/releases/gradle-plugin#library-classes-shrunk

Also devs will have to upgrade Android Studio to Jellyfish | 2023.3.1

Copy link
Member Author

Choose a reason for hiding this comment

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

Minifying apk and upgrading to the latest software are good things, no?

@Jean-BaptisteC does it work on all your devices? @rtsisyk can also run it on monkeys if necessary, but IMO it would be naturally tested in master, and then in betas. In case of any issues found the commit can be easily reverted.

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree that there is no need to rush. The previous upgrade triggered significant ripple effects and led to multiple crashes, distracting devs for a couple of days without providing any business value to the project.

Copy link
Member Author

Choose a reason for hiding this comment

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

Postponing issue discovery for later is also not a good long-term strategy. Don't forget about pros of the upgrade: https://developer.android.com/studio/releases/fixed-bugs/studio/2023.3.1

Copy link
Contributor

Choose a reason for hiding this comment

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

Android Studio can be upgraded without upgrading the plugin. I don't spare cycles to waste on testing every minor new version of Gradle plugin. The last time this careless bumping of versions caused regressions with strings. It is not merge-and-run story.

Copy link
Contributor

Choose a reason for hiding this comment

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

I've upgraded to 2023.3.1 and compiled this branch for testing.

Copy link
Member Author

Choose a reason for hiding this comment

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

@rtsisyk can you please check and help with fixing the linter error?

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.

None yet

3 participants