Killing the simulators the issue disappear, but of course in a CI environment is not the best way to solve this issue.
It seems to be the one working method. We setup our CI to kill simulator after each test.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: