-
Notifications
You must be signed in to change notification settings - Fork 219
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
Can't upgrade firebase_core to 3.4.0, because macOS deployment target #1116
Comments
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
The upgrade to the Dart package firebase_core 3.4.0 (from 3.3.0) leads to the CocoaPods pod Firebase/CoreOnly 11.0.0 (from 10.29.0) and the further pod Firebase/Messaging 11.0.0 (from 10.29.0). That produces the following `pod update` error message when attempting to run `tools/upgrade pub`: ``` + pod update --project-directory=macos/ Update all pods Updating local specs repositories Analyzing dependencies firebase_core: Using Firebase SDK version '11.0.0' defined in 'firebase_core' firebase_messaging: Using Firebase SDK version '11.0.0' defined in 'firebase_core' [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging": In Podfile: firebase_messaging (from `Flutter/ephemeral/.symlinks/plugins/firebase_messaging/macos`) was resolved to 15.1.0, which depends on Firebase/Messaging (~> 11.0.0) Specs satisfying the `Firebase/Messaging (~> 11.0.0)` dependency were found, but they required a higher minimum deployment target. ``` Fundamentally that should be fixable, but with some effort just now I wasn't able to actually increase that minimum deployment target in a way that satisfied CocoaPods so as to resolve this error. So, filed zulip#1116 for that. Meanwhile, let our other upgrades proceed.
Log
Changes is needed inside the |
In addition to Specifically, newer (You can demonstrate this by bumping |
Fixes zulip#1116. Done by changing the line in the Podfile, and following the (recently added) comment there by changing a setting in the Xcode GUI. The Podfile change seems to be the only thing missing when Greg attempted this bump: (from zulip#1116) > Naturally we're happy to bump up our minimum macOS deployment > target — 10.15 is from 2019, and even increasing to last year's > macOS 14 would be perfectly fine. But I spent a few minutes just > now attempting to do so — editing the `MACOSX_DEPLOYMENT_TARGET = > 10.14;` lines in the `project.pbxproj` file so they say 10.15 (or > 13.0) instead, then also tried setting it in Xcode which added > some new lines of that form — and the error persisted. (Perhaps > there's somewhere *else* that `pod update` is looking? Perhaps it > has a cache of some kind that it fails to update?)
As Greg said in zulip#1116: > 10.15 is from 2019, and even increasing to last year's macOS 14 > would be perfectly fine.
Fixes zulip#1116. Done by changing the line in the Podfile, and following the (recently added) comment there by changing a setting in the Xcode GUI. The Podfile change seems to be the only thing missing when Greg attempted this bump: (from zulip#1116) > Naturally we're happy to bump up our minimum macOS deployment > target — 10.15 is from 2019, and even increasing to last year's > macOS 14 would be perfectly fine. But I spent a few minutes just > now attempting to do so — editing the `MACOSX_DEPLOYMENT_TARGET = > 10.14;` lines in the `project.pbxproj` file so they say 10.15 (or > 13.0) instead, then also tried setting it in Xcode which added > some new lines of that form — and the error persisted. (Perhaps > there's somewhere *else* that `pod update` is looking? Perhaps it > has a cache of some kind that it fails to update?)
As Greg said in zulip#1116: > 10.15 is from 2019, and even increasing to last year's macOS 14 > would be perfectly fine.
When I try upgrading our dependencies with
tools/upgrade pub
, I get the following error from CocoaPods:This appears to correspond to the following release note:
https://firebase.google.com/support/release-notes/ios#version_1100_-_july_30_2024
saying version 11.0.0 of the Firebase Apple SDK started requiring a minimum deployment target of macOS 10.15.
Naturally we're happy to bump up our minimum macOS deployment target — 10.15 is from 2019, and even increasing to last year's macOS 14 would be perfectly fine. But I spent a few minutes just now attempting to do so — editing the
MACOSX_DEPLOYMENT_TARGET = 10.14;
lines in theproject.pbxproj
file so they say 10.15 (or 13.0) instead, then also tried setting it in Xcode which added some new lines of that form — and the error persisted. (Perhaps there's somewhere else thatpod update
is looking? Perhaps it has a cache of some kind that it fails to update?)So further debugging is required.
Meanwhile, we'll be holding back
firebase_core
at 3.3.0 rather than 3.4.0 (and so holding back the other Firebase-related packages too), because that's the upgrade that triggers this.The text was updated successfully, but these errors were encountered: