fix(firebase_auth): compile Android Kotlin without checker-qual on inferred types

[SelaseKay]

Description

:firebase_auth:compileDebugKotlin fails on Kotlin 2.4 when IdTokenChannelStreamHandler infers the IdTokenListener parameter type. com.google.firebase:firebase-auth class files reference @UnknownInitialization but do not declare org.checkerframework:checker-qual, so the inferred type is inaccessible.

Giving the SAM lambda an explicit FirebaseAuth parameter type is enough — Kotlin no longer infers the annotated type. Confirmed on Kotlin 2.4.10 with no checker-qual on the classpath.

The auth example is bumped to Gradle 8.14, AGP 8.11.1, and Kotlin 2.4.10 so CI compiles the language version that turns this from a 2.3 warning into an error.

Upstream packaging issue: firebase/firebase-android-sdk#8557

Related Issues

• Fixes [firebase_auth] compileDebugKotlin fails: checker-qual missing for @UnknownInitialization on inferred type #18608

Checklist

• 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.

This is a Gradle/Kotlin compile fix; there is no Dart behavior change to cover with an integration test. The example toolchain bump makes e2e-auth Android compile with Kotlin 2.4.

Breaking Change

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

Test plan

• :firebase_auth:compileDebugKotlin fails on Kotlin 2.4.10 without the explicit type
• Same task succeeds on Kotlin 2.4.10 with { auth: FirebaseAuth -> } and no checker-qual
• Auth Android e2e / example APK still builds on CI

[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.