Failed to authorize rights (0x1) with status: -60007.

Question

Created Mar ’16

Replies 6

Boosts 0

Views 1.4k

Participants 7

I found that Xcode 7.3 is no longer able to launch unit tests requiring iOS simulator. Xcode 7.2.1 was able to. I am seeing this with GitLab-CI and using a runner on my iMac where I updated to Xcode 7.3 two days ago:

You now get the error message after the unit test build:

Failed to authorize rights (0x1) with status: -60007.

For some reason OS X now requires some user interaction when launching the simulator which is not possible because there is no interaction allowed, the runner runs as daemon. If you google for this message then you find solutions related to the keychain. But in this case no code signing occurs since this is a simulator build.

Anybody know how to work around the issue? Is that an Xcode 7.3 bug?

cheers

Oliver

Boost

Answer 1

Kevin Harwood MM OP

Mar ’16

I'm also seeing something similiar. Seems to only be tests. I can also see some test suites pass, then it hangs.

0

Answer 2

devalr OP

Mar ’16

So I was running into the same problem with Jenkins and I had a build step that ran "open -a simulator" prior to running the unit tests. (I think I had read somewhere that this would open the simulator in a way that got around Jenkins running headless).

I was banging my head against it so I redownloaded Xcode 7.2.1 to verify it worked still and used xcode-select to switch versions, then I switched back and saw the problem still appeared in 7.3. I had noticed that a problem in 7.3 appeared to be that multiple simulators were getting opened when I rand the build.

Finally I removed the "open -a simulator" command and it seems to work. I still have one jenkins build that fails to sense when the unit tests finish running, but I haven't had a problem getting the tests to run. The build that still hangs does not swap the app delegate for a separate testing app delegate. (something like this: http://qualitycoding.org/app-delegate-for-tests/) So I'm hoping that could be the issue. Also note that my projects that only test libraries never exhibited bad behavior, they were always able to run the tests.

That's as far as I've got so far. I hope it helps!

0

Answer 3

drewcrawford OP

Mar ’16

Try updating your runner. In particular, see the Limitations on OSX section here: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/install/osx.md

> In order to upgrade the LaunchAgent configuration, you need to uninstall and install the service

Something about running through those steps resolved the problem for me.

0

Answer 4

wooliedev OP

May ’16

We are seeing the same issues. If we run the entire series of unit tests locally (instead of from the Jenkins job) then it works fine.

If we run it from Jenkins then we get the error.

Guessing this has a lot to do with how our Jenkins boxes are set up to launch the xcodebuild process.

0

Answer 5

jcollas-travelers OP

Aug ’16

Just ran into this issue, OS X 10.11.5, Xcode 7.3.1, running tests from a Jenkins slave, v. 1.639. Was there any resolution?

0

Answer 6

esay OP

Apr ’17

This is Xcode version related to me. Changing to Xcode 8.0 solve the problem.

0