[SelaseKay]

Description

Gradle 9 deprecates Groovy space-assignment syntax for properties (prop value / prop(value)), and Gradle 10 is scheduled to remove it. FlutterFire Android plugin build.gradle files still used that form for group, version, namespace, and (in some plugins) buildConfig, which produces deprecation warnings on every consumer build under Gradle 9 and will break configuration under Gradle 10.

This PR switches those assignments to explicit prop = value across all Android plugins. The same leftover form in example and test apps (minSdkVersion and coreLibraryDesugaringEnabled) is updated to match. The change is compatible with Gradle 8.x.

Remaining plugin lines such as compileSdkVersion / minSdkVersion project.ext.minSdk are AGP methods, not the Gradle property syntax this issue covers, and are left unchanged.

Related Issues

Fixes #18832

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

Test plan

• Confirm plugin android/build.gradle files no longer use space-assignment for group, version, namespace, or buildConfig.
• Confirm example/test leftovers (minSdkVersion Math.max(...), coreLibraryDesugaringEnabled true) now use =.
• Build a Flutter Android app that depends on FlutterFire with Gradle 9.x using ./gradlew help --warning-mode all and confirm the space-assignment deprecation no longer points at FlutterFire plugin build.gradle lines.
• Smoke-configure/build with Gradle 8.x to confirm backwards compatibility.

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.