-
Bug
-
Resolution: Unresolved
-
Major
-
Xcode 4.4.1, OSX Mountain Lion
Project builds fine when not setting technical version to something like ${BUILD_NUMBER}.
When setting technical version in build step, the following error gets output:
/usr/bin/agvtool new-version -all 71
There are no Xcode project files in this directory. agvtool needs a project to operate.
FATAL: Could not set the CFBundleVersion to: 71
Build step 'XCode' marked build as failure
I use an Xcode Workspace File and build a Scheme. The workspace file is not in the same folder as my main project file. Maybe this is the problem?
[JENKINS-15118] Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project
Fabian E
created issue -
Jonathan Brown
added a comment - My xcodeproj is in a subfolder of the folder containing the xcworkspace. I had to set the Advanced Xcode Build Options > Xcode Project Directory to the name of the project's subfolder. Then set the Xcode Workspace File to a relative path from there: e.g., ../MyWorkspace.
(I also had to move my Scheme from the Project to the Workspace, and update the relative path to my Code Signing & OSX Keychain Options > Embedded Profile.)
Jonathan Brown
added a comment - My xcodeproj is in a subfolder of the folder containing the xcworkspace. I had to set the Advanced Xcode Build Options > Xcode Project Directory to the name of the project's subfolder. Then set the Xcode Workspace File to a relative path from there: e.g., ../MyWorkspace.
(I also had to move my Scheme from the Project to the Workspace, and update the relative path to my Code Signing & OSX Keychain Options > Embedded Profile.) 
Sharon Bamani
added a comment - I get the same error.
When working with "Xcode Workspace File",which is not at the jenkins workspace (for example dirA/dirB ) without specifying the "Xcode Project Directory":
$ /usr/bin/agvtool new-marketing-version 0.0.109
There are no Xcode project files in this directory. agvtool needs a project to operate.
FATAL: Could not set CFBundleShortVersionString to: 0.0.109
Sharon Bamani
added a comment - I get the same error.
When working with "Xcode Workspace File",which is not at the jenkins workspace (for example dirA/dirB ) without specifying the "Xcode Project Directory":
$ /usr/bin/agvtool new-marketing-version 0.0.109
There are no Xcode project files in this directory. agvtool needs a project to operate.
FATAL: Could not set CFBundleShortVersionString to: 0.0.109 
James Parker
added a comment - I'm not getting an error when I set this. Instead it's just not changing the version / build number from what is actually set in the project settings. It was working fine until I updated my build server to Yosemite and installed Xcode 6 alongside Xcode 5. I'm running the latest version of the Xcode plugin.
James Parker
added a comment - I'm not getting an error when I set this. Instead it's just not changing the version / build number from what is actually set in the project settings. It was working fine until I updated my build server to Yosemite and installed Xcode 6 alongside Xcode 5. I'm running the latest version of the Xcode plugin. 
lacostej
added a comment - James, do you have more logs ? James Parker
made changes -
| Attachment | New: jenkinslogfile.txt [ 28353 ] |
See the below issue for further information about the issues I'm having.
https://issues.jenkins-ci.org/browse/JENKINS-26368
James Parker
added a comment - - edited See the below issue for further information about the issues I'm having.
https://issues.jenkins-ci.org/browse/JENKINS-26368 
Alvin Wong
added a comment - Running into similar issue I think. Project builds fine but the technical version is not changed in the info.plist.
Alvin Wong
added a comment - Running into similar issue I think. Project builds fine but the technical version is not changed in the info.plist. Alvin Wong
made changes -
| Attachment | New: log.txt [ 28635 ] |
All agvtool command executions are executed from the projectRoot directory.
The projectRoot is currently either the workspace (default) or the relative Xcode project directory
I don't see why setting the workspace directory should prevent agvtool from working. Could you check in your job output if the project root is properly defined ? Also try running the agvtool from the command line.