Hey there! Did you find any workaround around this?

@jbentonGx and any way to catch the error? I'm using fastlane multi_scan to run my uitests, which has a retry mechanism for the failed tests. The fact that the error described above happened along the batch, makes the multi_scan interpreted everything as failed and loses information around the already passed tests. It assumes a build issue occured, so either fails or I can order to try again but it repeats all the tests again. If this error does not occur only the failing tests are ran again