Quentin Renard

Can I close this PR or will you be working on it in the future?

I have not tried to write integration tests for an astilectron based app but here are 2 issues that could point you to the right direction: https://github.com/asticode/go-astilectron/issues/170 https://github.com/asticode/go-astilectron/issues/90

I think the idea of this PR is: 1) You set a custom `Executer` that does not execute `astilectron` 2) You remove the TCP timeout so that `go-astilectron` doesn't return...

If you use the [Adapter](https://github.com/asticode/go-astilectron-bootstrap/blob/master/options.go#L12) attribute of `bootstrap.Options`, you should be able to manipulate your `*astilectron.Astilectron` and therefore use `a.SetExecuter`.

If that's not too much trouble for you, I'm curious what the PR would look like. I can't promess it will be merged though

When using the bundler, you can use the `-a` flag to indicate the path to your local `astilectron` folder. That way, it's **your** astilectron version that is bundled.

Unfortunately this is not possible as of right now. Out of curiosity, is it a cmd you're spawning that requires `sudo` privileges? If so, are you spawning it using GO...

Unfortunately I don't see any solution for this. I've found [this NodeJS package](https://github.com/jorangreef/sudo-prompt) that allows executing scripts needing sudo from JS but that would defeat the purpose of udp listening...

Out of curiosity, why do you need to manually bundle to make your solution work ?

> I actually figured that using Info.plist I was able to run the program with sudo, but I haven't seen any similar documentation support of asticode-bundler for Windows (for example,...