{"id":32674,"date":"2021-06-02T16:03:01","date_gmt":"2021-06-02T20:03:01","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=32674"},"modified":"2021-06-05T21:03:01","modified_gmt":"2021-06-06T01:03:01","slug":"slow-testing-with-xcode-12-5-and-big-sur","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/06\/02\/slow-testing-with-xcode-12-5-and-big-sur\/","title":{"rendered":"Slow Testing With Xcode 12.5 and Big Sur"},"content":{"rendered":"

OlKir1143<\/a>:<\/p>\n

When running app in iOS 14.5 simulator launch takes incredibly long time (more than 30 seconds). In comparison launching installed app in simulator - 2 seconds, launching app on the real device (iOS 14.4) - 6 seconds.<\/p>

[…]<\/p>

When running against simulator Xcode says “launching app”, “attaching to app”, and then “running app”, at the running app stage we get a ~30 second pause. debugserver at 100% activity at that time.<\/p><\/blockquote>\n\n

Via Chris Fish<\/a>:<\/p>\n

I have noticed that our regular dev lifecycle has tanked significantly since updating to 11.3. It takes up to 10 seconds to attach the debugger. If I run the app without attaching the debugger automatically it flies.<\/p><\/blockquote>\n\n

This is reported as starting with macOS 11.3. I didn’t see any problems with that version, but since updating to macOS 11.4 I’ve seen incredible slowness testing my Mac code. Running an individual unit test used to be almost instantaneous. Now there is a delay of 10 seconds or so between launching xctest<\/code> (i.e. when Xcode starts showing “Testing…”) and when the test actually begins running. Turning off “Debug executable” doesn’t help. Sampling the process shows that xctest<\/code> is waiting for the access()<\/code> call, as it tries to load my test bundle. Meanwhile, the tccd<\/code> process pegs the CPU.<\/p>\n\n

I guess the problem must be triggered by something<\/em> in my project—or perhaps just its (modest though non-trivial) size—since it doesn’t occur with a fresh project (though even that has high CPU use for tccd<\/code>). I’m not sure what TCC doesn’t like. The test bundle and all the frameworks that it links to are code signed. The delay occurs on three different Macs, one of them a clean installation.<\/p>\n\n

Another Xcode 12.5 issue: the “Run ‘Test\/Class’” command (Command-Control-Option-U) is always disabled, even though Xcode shows the tests and I can run them by clicking the diamond.<\/p>\n\n

Previously:<\/p>\n