My Swift app uses a 3rd party framework to control a peripheral. The framework was written for Objective-C so I created a bridging header to make it work in Swift. It all works perfectly when I run the app within Xcode, or when I build the app and run it directly from the Debug folder.But when I archive the app and then export a copy to my hard drive, some (but not all) calls to the 3rd party framework fail. [details removed]UPDATE: Issue is App Sandbox. Debug builds had it off. Archives had it on. Debug builds with Sandbox break too.The 3rd-party framework is set as "embedded content" with "embed and sign" turned on. Calls to it return basic data, like version number. This framework needs to communicate with a 3rd party app to actually talk to the USB peripheral. That may be the hurdle; is there a way over it?Note: When the 3rd party framework calls out to initialize a link to the 3rd party app (and fails) I see a "Connect Error: No such file or Directory" log entry in the Xcode output window.