ancient vortex
I've developed an app that allows me to run other projects on my machine as needed. It's basically just a bunch of config and then when you use the UI to run one of the other applications, it uses child_process.spawn with the config for the given app to start it. (there's a little more to it, but thats the gist). Everything is working exactly how I want it to while developing the app and I've just started working on building a distributable version. I'm on macOS and the build succeeds with electron-builder. I get the .app output and I can run it and see the windows just fine. However when I use my UI to run one of the applications, they don't actually start. I have some logic to provide feedback when there is an error starting an app and that's exactly what's happening, when I try to run an app, it turns into my "error" color immediately.
Something at the step where I'm calling child_process.spawn to run the app is not working in the built app, but works fine during development. Wondering if there are any signing/security considerations I might be missing during build in order to be allowed to launch child processes? Otherwise, what would be the easiest way to debug the production app? I read some older posts about being able to debug the console logs from the main process by attaching a remote debugger using lldb. When I went through those steps, the child processes were spawned successfully again... Should I just add some console logging around the problem area and write them to a file?
Appreciate any tips, thanks!
