fix(auth): fix inconsistence in casing in the native iOS SDK and Web SDK

[Lyokone]

Description

checkActionCode on iOS always returns ActionCodeInfoOperation.unknown since Firebase iOS SDK 11.12.0. The upstream SDK's actionCodeOperation(forRequestType:) was changed from matching "VERIFY_EMAIL" to "verifyEmail", but the REST API still returns SCREAMING_SNAKE_CASE. Since the raw requestType is internal to the SDK and not exposed on FIRActionCodeInfo, we work around this by making a direct REST call to the Identity Toolkit API when the operation comes back as unknown, and mapping both case formats ourselves. The workaround is self-disabling: once the upstream fix lands, the iOS SDK won't return .unknown anymore and the fallback path is never taken.

Related Issues

• Fixes [firebase_auth]: ActionCodeOperation mapping fails due to incorrect requestType casting in ActionCodeInfo #17452
• Upstream bug: ActionCodeOperation mapping fails due to incorrect requestType casting in ActionCodeInfo firebase-ios-sdk#15010 (closed without fix)
• Introduced by: Changed actionCodeOperation types firebase-ios-sdk#14668

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.

Breaking Change

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

[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

Customization

To customize 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 counter productive. 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.