Location of `download-cli.sh` changed in Xcode 16.3

[robb]

Summary

Couldn't install the CLI through the Xcode 16.3 beta.

The folder being checked is

~/Library/Developer/Xcode/DerivedData/<# Project #>/Build/Intermediates.noindex/CommandPluginIntermediates/Install CLI.output/../../checkouts/apollo-ios/scripts/download-cli.sh

but the actual file lives at

~/Library/Developer/Xcode/DerivedData/<# Project #>/SourcePackages/checkouts/apollo-ios/scripts/download-cli.sh

Invoking the script manually from the terminal seemed to work just fine.

Version

1.18.0

Steps to reproduce the behavior

• Open a project in Xcode 16.3
• Right click the project, select the Install CLI option
• Nothing installs

Logs

Showing All Messages
working directory:
   /Users/robb/Developer/linear-app/mobile-ios
tool mapping:
tool paths:
   /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
   /Applications/Xcode-beta.app/Contents/Developer/usr/bin
   /bin
   /sbin
   /usr/bin
   /usr/sbin

Installing Apollo CLI Plugin to Xcode project Linear
/bin/sh: /Users/robb/Library/Developer/Xcode/DerivedData/Linear-fgcjeqtuzqjldncybbmkkcmdjibu/Build/Intermediates.noindex/CommandPluginIntermediates/Install CLI.output/../../checkouts/apollo-ios/scripts/download-cli.sh: No such file or directory

Installing Apollo CLI Plugin to Xcode project Linear

/bin/sh: /Users/robb/Library/Developer/Xcode/DerivedData/Linear-fgcjeqtuzqjldncybbmkkcmdjibu/Build/Intermediates.noindex/CommandPluginIntermediates/Install CLI.output/../../checkouts/apollo-ios/scripts/download-cli.sh: No such file or directory

Anything else?

No response

[AnthonyMDev]

Thank you for the report! We'll look into this and get a patch out before Xcode 16.3 goes public.

[calvincestari]

I did some investigation of this issue and it looks like Xcode 16.2 had the plugins 'work' from within the SourcePackages directory; that made sense why we could simply backtrack (../../) two folders and get access to checkouts. Xcode 16.3 now has a separate directory that it gives the plugin complete control over, which is outside of SourcePackages.

I also noticed that XcodePluginContext.pluginWorkDirectory and XcodePluginContext.xcodeProject.directory are marked as deprecated, which puts in jeopardy the method we use to find the download script and the project path passed into the script used as the destination for the CLI binary. Not sure how we'd resolve this yet.