I have a xcodebuild task that fails with the error: xcodebuild: error: '' is not a workspace file. But, the job does not contain a worskspace file, and neither does the project. I use a project file.
It seems that everything works just fine, and the part that fails shouldn't run at all, since i didn't enter a workspace file in configuration. Or am i missing something here?
The log (masked):
10-Oct-2017 11:26:34 Signing Identity: "iPhone Developer: Build Server (**********)"
10-Oct-2017 11:26:34 Provisioning Profile: "iOS Team Provisioning Profile: ********"
10-Oct-2017 11:26:34 (*************************************)
10-Oct-2017 11:26:34
10-Oct-2017 11:26:34 /usr/bin/codesign --force --sign *************************************** --entitlements /Volumes/Bamboo/bamboo-agent-home/xml-data/build-dir/TES-IOSTE-JOB1/iOSTestApp/build/iOSTestApp.build/Release-iphoneos/iOSTestApp.build/iOSTestApp.app.xcent --timestamp=none /Volumes/Bamboo/bamboo-agent-home/xml-data/build-dir/TES-IOSTE-JOB1/build/iOSTestApp.app
10-Oct-2017 11:26:35
10-Oct-2017 11:26:35 Validate /Volumes/Bamboo/bamboo-agent-home/xml-data/build-dir/TES-IOSTE-JOB1/build/iOSTestApp.app
10-Oct-2017 11:26:35 cd /Volumes/Bamboo/bamboo-agent-home/xml-data/build-dir/TES-IOSTE-JOB1/iOSTestApp
10-Oct-2017 11:26:35 export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
10-Oct-2017 11:26:35 export PRODUCT_TYPE=com.apple.product-type.application
10-Oct-2017 11:26:35 builtin-validationUtility /Volumes/Bamboo/bamboo-agent-home/xml-data/build-dir/TES-IOSTE-JOB1/build/iOSTestApp.app -validate-for-store
10-Oct-2017 11:26:35
10-Oct-2017 11:26:35 ** BUILD SUCCEEDED **
10-Oct-2017 11:26:35
10-Oct-2017 11:26:35 User defaults from command line:
10-Oct-2017 11:26:35 IDEArchivePathOverride = /Volumes/Bamboo/bamboo-agent-home/xml-data/build-dir/TES-IOSTE-JOB1/build.xcarchive
10-Oct-2017 11:26:35
10-Oct-2017 11:26:35 Build settings from command line:
10-Oct-2017 11:26:35 SDKROOT = iphoneos10.3
10-Oct-2017 11:26:35
10-Oct-2017 11:26:35 xcodebuild: error: '' is not a workspace file.
We are using Bamboo 6.0.01
I am also facing same issue. can anybody help?
I added only project file path not workspace path, as I am not using workspace. but it is showing this "xcodebuild: error: '' is not a workspace file". error.
I guess it is still trying to pick workspace path which it shouldn't.
any help will be appreciated.
Have created the bug report https://jira.atlassian.com/browse/BAM-19885
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same problem, Have you guys find solution for this?
User defaults from command line: | |
16-May-2018 11:05:02 | IDEArchivePathOverride = /Users/me/Desktop/Builds/iOS-2.xcarchive |
16-May-2018 11:05:02 | |
16-May-2018 11:05:02 | Build settings from command line: |
16-May-2018 11:05:02 | SDKROOT = iphoneos11.3 |
16-May-2018 11:05:02 | |
16-May-2018 11:05:02 | xcodebuild: error: '' is not a workspace file. |
Failing task since return code of [/usr/bin/xcrun -sdk iphoneos11.3 xcodebuild -workspace -scheme Staging -sdk iphoneos -configuration Staging archive -archivePath /Users/me/Desktop/Builds/iOS-2.xcarchive]
As you can see the line from logs does include -workspace key word. However, I do not use workspace ;/ I do use xcodeproj file.
That's what I have specify in my JOB.
It does work if I won't generate an IPA file. If I do select to generate IPA file it fails on this line
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jonas,
Check what is the command ran in the build logs?
Does the same work from terminal in the same build working directory?
If there is a problem with the command (spacing for example), check the task configuration to make sure it is fixed.
Try the command with quotes and see if that spaces are causing this by chance.
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.