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
xcpretty: command not found #12331
Comments
I did want to add that xcpretty occurs on my Xcode server machine in /usr/local/bin it does not reside in /usr/bin In my trigger script, I have to invoke fast lane with the line Thanks, kerwin |
@kerwinAPG I have never run Xcode server but it looks like this might be a configuration issue with your machine. It looks like one of your things is installed as/with a root account and the other is running with your user account? |
I found a fix for this was to add to my trigger script the following: PATH="/usr/local/bin:$PATH" and then as the Fastfile invokes gym, that the scripts will search the usr/local/bin/ for commands rather than the default usr/bin/ location. This is necessary for Xcode Server where a test user is created. I credit Honza Dvorsky for this solution. This fix was an adaptation of one he suggested in his pages about using Xcode Server Bot Triggers for Continuous Integration. https://honzadvorsky.com/articles/2015-08-17-17-30-xcode_server_tutorials_3_prebuild__postbuild_scripts/ |
@kerwinAPG Ah, so looks like it was a configuration issue with which user was executing fastlane. Glad you got it solved! Happy fastlaning 🚀 |
New Issue Checklist
Issue Description
I am getting the xcpretty: command not found error during build_app stage. I am running this as trigger in Xcode server. I can run the Fastfile beta directly on that machine without error, but when running through Xcode trigger, I see this. I have read a previous issue regarding this issue. I tried a
sudo gem install xcpretty --verbose
and verified that it installed. but it does not address the issue. That issue last dated Jul 2016 and was closed.
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: