need held while installing apollo (version 1.0.3) Via cocoapods ,getting error as follows.

[bhushanrocks412]

Hi i am getting following error in terminal while installing Apollo version '1.0.3' via cocoapods in my ios swift application,
can anyone help me with this. Thanks

pod install
Analyzing dependencies
Downloading dependencies
Installing Apollo (1.0.3)
[!] /bin/bash -c
set -e
make clean build-cli-for-cocoapods
cp .build/release/apollo-ios-cli apollo-ios-cli
chmod +x apollo-ios-cli

swift package clean
swift build --product apollo-ios-cli -c release -Xswiftc -DCOCOAPODS
/Users/bhushandeshmukh/Library/Caches/CocoaPods/Pods/Release/Apollo/1.0.3-936d4: error: package at '/Users/bhushandeshmukh/Library/Caches/CocoaPods/Pods/Release/Apollo/1.0.3-936d4' is using Swift tools version 5.6.0 but the installed version is 5.5.0
make: *** [build-cli-for-cocoapods] Error 1

[calvincestari]

Hi 👋🏻 - the error itself is quite clear..

error: package at '/Users/bhushandeshmukh/Library/Caches/CocoaPods/Pods/Release/Apollo/1.0.3-936d4' is using Swift tools version 5.6.0 but the installed version is 5.5.0

You need to use a minimum Swift version of 5.6. This ships with Xcode and therefore you need to use a minimum Xcode version of 13.3. You can see the version of Swift shipped with each Xcode version from here.

The error is being thrown because the make command builds the CLI which is a Swift package and in the Package.swift file you can see that the swift-tools-version required is 5.6.

@bhushanrocks412 - is there a reason you wouldn't be able to upgrade your version of Xcode?

Update - More context here, Swift 5.6 is needed for the SPM plugins.

[calvincestari]

I see that the podspec spec does allow for specifying a minimum Swift version using swift_versions, I think we should consider adding this to our podspec to avoid this kind of mismatch in the future.

[calvincestari]

Turns out we already use swift_version in the podspec, but it is out of date. We'll get that fixed.

[bhushanrocks412]

Thanks @calvincestari & @AnthonyMDev ... after upgrading Xcode to latest version, issue is now resolved. appreciate your response. there was no reason to not upgrade to latest Xcode version.