Cameron Cooke
Cameron Cooke
Will give that a try, thanks.
@MagifyApps Great idea, love it!
I've seen this issue with xcode projects too, I had to open the project and build on Xcode first before Sweetpad would work. Strange.
@hyzyla any thoughts on this? I'm unable to build any local Swift package in my workspace.
Any movement on this?
Can you provide me more detail of the use cases you have in mind?
Sorry for the previous PR originally I thought the issue was a code-signing one and went down a rabbit hole. This fix is much simpler and directly fixes my issues.
Only, problem I'm seeing with this is that we lose the stderr and stdout. I could open the executable directly instead of app bundle and this would open an external...
Ok, one solution that works is to use `lldb` instead of `open` or executing the application directly. This mirrors Xcode's "Run" (Cmd+R) action which builds, runs and attaches a debugger....
That's interesting, I personally like the launching with debug session option as this not only fixes the issues I was having it's also representative to how Xcode works when running...