-
Notifications
You must be signed in to change notification settings - Fork 726
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
Xcode Install CLI fails for versions >=1.8 #3333
Comments
@pjf-amexgbt Hmm the error seems to think its an issue unpacking the .tar.gz, but it could honestly also be a download issue like you mentioned as well. I can look into some and see if I can reproduce, and also maybe improve the error logging some to be more clear, in the meantime can you take a look in your project directory while running the plugin and see if you see a |
Not relevant since we only changed the CLI installation to download the binary from |
The
|
Closing this since there hasn't been any activity, if this is still an issue feel free to reopen. |
Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better. |
@BobaFetters Apologies for the slow response, forgot to link accounts so didn't get a notification. Yeah it does seem to be a download issue. A VPN block was my guess, but I did test with I did a bit of additional investigation playing with "download-cli.sh" am getting some odd results.
So it seems it may be caused by some combination of running it through Xcode and the wonderful corporate laptop "Security" 🫠 However, wondering if there's a reason to download the file? Especially when it seems to (currently) be included in the repo: https://github.com/apollographql/apollo-ios/tree/main/CLI |
Also, I apparently am unable to re-open. Feel free to do so, I should be more responsive now :) |
@pjf-amexgbt no problem, hmmm yea I guess maybe its an issue with the curl command when run through xcode then. Something I can definitely look into. As far as the need to download the file, originally the file was packed with the library and then unzipped by the plugin, we wanted to reduce the downloaded library size by removing the built in tar.gz and having the plugin download it instead, although we ran into an issue with the Cocoapods support still needing the built-in tar.gz. This is something we will revisit and see if we can either fix the download issue and remove the issue with Cocoapods to have the included tar.gz or we may just revert back to having the plugin work based on the built-in tar.gz |
Thank you for looking into it! It would be nice to have the option of building it from source. It seems that option was removed with the CLI changes (and also the "Build it Yourself" section is now out of date here 🙃 docs/ios/code-generation/codegen-cli/#installation) |
Ah thanks for the callout on the documentation needing updated, will take care of that. As far as being able to build it yourself, that isn't possible with the plugin anymore because of the changes that were made to our git structure to modularize our libraries, more info on that here TLDR; the executable is now part of a separate repo/spm package than the main client library that contains the plugin. So technically you could still download that package and build it yourself you would just need to ensure you pull a matching version. Also it looks like we should be able to fix the Cocoapods issue we had so the plan currently is to move forward with fixing that and then working on fixing the curl command for the plugin to resolve the issue you are seeing. |
Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better. |
Summary
Xcode is unable to download/install CLI from Xcode from version 1.8 on.
This is what happened in previous versions (including 1.7):
This is what happens now (including 1.9):
Version
1.9
Steps to reproduce the behavior
Now:
Logs
No response
Anything else?
Confirmed with a coworker and it's happening for them as well. It's possible this is being stopped by the corporate VPN, but it's unclear based on the error shown
The text was updated successfully, but these errors were encountered: