I wish I could; still the error surfaces while the internal apple libraries are executed, as you may see in the published logs that do not even mention files in my own project, but rather an exotic FigCaptureSourceRemote.m file, when my code is just Swift!
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: