-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CocoaPods 1.16.2 #13989
CocoaPods 1.16.2 #13989
Conversation
Looks like There's a potential workaround at CocoaPods/CocoaPods#12664 (comment) |
Removing |
Settings diff:
|
The Firestore build issue is by changing See https://github.com/CocoaPods/Specs/blob/master/Specs/c/8/7/gRPC-C++/1.67.0/gRPC-C++.podspec.json#L32 and https://github.com/CocoaPods/Specs/blob/master/Specs/3/8/6/abseil/1.20240722.0/abseil.podspec.json#L22 |
Many thanks @paulb777 |
I am able to workaround with the following |
Add this to your Podfile if you want a workaround, note you may already have a post_install section, so you would just use the inner part(s): [note: this was edited to be post_install do |installer|
installer.pods_project.targets.each do |target|
if target.name == 'abseil'
Pod::UI.puts "Workaround: Configuring abseil to use gnu++14 language standard for cocoapods 1.16+ compatibility".yellow
Pod::UI.puts " Remove workaround when upstream issue fixed https://github.com/firebase/firebase-ios-sdk/issues/13996".yellow
target.build_configurations.each do |config|
config.build_settings['CLANG_CXX_LANGUAGE_STANDARD'] = 'gnu++14'
end
end You will need to run |
This succesfully solved the issue. Thank you so much |
@KevinSinSH This works for me. Please try this one |
This doesn't work for me in a flutter project |
6d370c3
to
86575c6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. The SPM CI failures look unrelated (probably a flake).
Yes, thanks. I used the one commented here and solved, i guess it is basically the same. But I am unsure when this issue is fixed and can remove the workaround post install script. |
After updating to CocoaPods 1.16.2, the issue is fixed. The post_install and any other workarounds can be removed |
This PR worked through integration testing of CocoaPods 1.16.*, finding issues with 1.16.0 and 1.16.1 before settling on 1.16.2