On normal user systems, the first time in a given login session that any such Apple-code-signed debugger or performance analysis tools are used to examine one of the user’s processes, the user is queried for an administator password for authorization.
You’ll also need to run: sudo DevToolsSecurity -enable This will eliminate one class of these authentication popups. Sometimes you may miss seeing it, but without these, the Simulator will give you an authentication prompt that never clears.Ī first solution to this (on Mavericks) is to run: sudo security authorizationdb write allow Secondly, the XCode Developer tools requires elevated privileges in order to execute all of the tasks on the Unit tests. It needs to be able to pop up the simulator, and will fail if you don’t have a user logged in - as it can’t do this entirely headless without a display. The first problem, is that you dohave to have the user that runs the builds also logged in to the console on that Mac build machine. I’ve been working to get a continuous integration pipeline set up for an iOS project, and to get unit tests & integration tests to run headlessly via gradle builds through a Thoughtworks Go server.Īn issue I’ve run into is where running the unit tests requires the iOS simulator to pop up on the build server, which then ends up hanging on the build.
starting agents with JNLP) but for other platforms like Thoughtworks Go and Team City, or even just running builds over ssh, it no longer works.Īpple is apparently working on a solution for such, stay tuned. Workarounds for doing continuous integration with Jenkins exist (i.e. Doing xcodebuilds over SSH is presently not supported on XCode 6. The post below works on XCode 5.1, but is broken when you move to XCode 6.
0 kommentar(er)
