[arifozgun]

Widens the GoogleSignIn-iOS requirement from 9.0.0..<10.0.0 to 9.0.0..<11.0.0 in both the Swift package and the podspec (~> 9.0 to >= 9.0, < 11.0), so apps can resolve GoogleSignIn 10, which allows gtm-session-fetcher 4.x and 5.x.

GoogleSignIn 10 requires iOS 15 and macOS 12, and SwiftPM rejects a package whose dependency needs a higher platform than the package declares. This raises the plugin minimums to iOS 15 / macOS 12 (matching Flutter 3.47), updates the macOS example deployment targets, and updates the google_sign_in README support table, following #13292.

Apps that also use firebase-ios-sdk 13 (no longer published to CocoaPods) need GoogleSignIn-iOS 10.1.0 or later, which includes google/GoogleSignIn-iOS#626 and widens App Check from 11.x to 11.0.0..<13.0.0. The range here admits 10.1.0.

Fixes flutter/flutter#194435

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

Versioning: google_sign_in only changes its README (support table) and macOS example, so it's listed under NEXT without a version bump, as in #13292.

Test exemption: manual dependency update with no plugin code changes. The existing native and integration tests run against GoogleSignIn 10 once SwiftPM or CocoaPods resolves it.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If both you and the PR author believe this PR qualifies for a test exemption, escalate to the tech lead for the changed area to review and apply the test-exempt label. All reviewers should feel empowered to ask for tests before escalating.

[gemini-code-assist]

Code Review

This pull request updates the minimum supported platform versions for the google_sign_in_ios package to iOS 15 and macOS 12 across the package configuration, podspec, Swift Package Manager configuration, and example projects. It also updates the package's Flutter and Dart SDK constraints to Flutter 3.47 and Dart 3.13, expands the GoogleSignIn-iOS dependency range to support version 10.x, and updates the documentation and changelogs accordingly. There are no review comments, and I have no feedback to provide.

[arifozgun]

Pushed be523b8 to fix Linux repo_checks: raising the Dart SDK floor to 3.13 changes dart format output for two google_sign_in_ios test files. The publishability failure was a side effect of that step leaving them modified.

The remaining failure is the version check on google_sign_in, which only changes its README support table and macOS example and is listed under NEXT, as in #13292. Could a reviewer add override: no versioning needed?

[jmagman]

override: no versioning needed: the google_sign_in change is README‑only

[arifozgun]

Merged main to resolve the CHANGELOG/pubspec conflict with 6.3.9.

I also widened the podspec to >= 9.0, < 11.0 to match the Swift package. The description said GoogleSignIn 10 isn't on CocoaPods trunk, but that was wrong: 10.0.0 and 10.1.0 are both published there.

GoogleSignIn-iOS 10.1.0 has since been released with google/GoogleSignIn-iOS#626 (App Check 12), so apps on firebase-ios-sdk 13 can resolve it with this range. The description is updated to match.

Could a maintainer re-add CICD?

[kishor-mainali]

Any updates on this, this is breaking our apps if we update the firebase plugins

[AmrTawfek]

One more case this unblocks, independent of Firebase: flutter_appauth 13.0.0 (stable since Oct 30) moved to AppAuth-iOS 3 and pins it exactly (Package.swift:15). Every GoogleSignIn-iOS 9.x release requires AppAuth-iOS 2.x (9.2.0 Package.swift:45-46), so with google_sign_in_ios 6.3.8 an app that uses both plugins can't move to flutter_appauth 13 under SwiftPM. GoogleSignIn-iOS 10.1.0 requires from: "3.0.0" (Package.swift:45-46), so the range in this PR covers that case as well.

For an app on firebase_core 5.1.0 and flutter_appauth 13.0.0, the package manifests resolve with this PR to GoogleSignIn-iOS 10.1.0, AppAuth-iOS 3.0.0, GTMAppAuth 6.0.0, app-check 12.0.0, gtm-session-fetcher 5.3.1 and firebase-ios-sdk 13.1.1. That's from the Package.swift files, not an Xcode build; it matches the build result reported in flutter/flutter#194435.

[ZoftPranav]

This issue is currently blocking our iOS builds. Could you please prioritize reviewing and merging this fix? We are unable to generate iOS builds until this is resolved. Your help in addressing this at the earliest would be greatly appreciated.