@silval3 there is not any way that I know of to catch the error. :cry: It is happening in the framework part of running the xcuitests. It would require a fix to the framework by Apple.

There is not a solution from Apple at this time. There are not currently any workarounds using the xcuitest framework and runner. If you made your own test runner, you might be able to run tests individually and clean up at the end / between test runs. Some other test frameworks have solutions like that built in.