We recently upgraded to Ventura and to our surprise, some of our development builds stopped working. After a lot of debugging, it turns out to be cause by the fact that Venture ships curl 7.86 (and git uses libcurl). Curl (and git) are broken because no longer honor the no_proxy environment variables. https://github.com/curl/curl/issues/9884

I am using electron-builder to build, sign, notarized, and publish my application. All of this works perfectly when I am directly connected to the Internet. When running this from my corporate network that require the use of a proxy server, electron-notarize, which spawns xcrun, gets a connect timeout when trying to upload the signed app to the iTunes server. How do I get xcrun to use the proxy server? I have the HTTPS_PROXY environment variable set to http://my.proxy.server.name:80 but xcrun is still trying to connect directly to the iTunes server.

I am trying to notarize my app using XCode's xcrun aitool but XCode appears to not be capable of honoring the MacOS proxy settings or the standard HTTP_PROXY/HTTPS_PROXY environment variables. It seems like people have been asking this same question for many years and Apple doesn't have any answer. Has anyone gotten this to work?

We are building an open source, electron-based application and using electron-builder's code signing support to sign our application (that is distributed outside of the App Store). Unfortunately, we seem to have hit an impasse due to what appears to be a limitation (or bug) of the underlying Apple codesign utility. Our application bundles a couple of other open source projects "installed versions" inside of it. These applications, as well as our own, include TXT files mixed in with binary files and at least a couple of them cannot me separated from the binary directory. If codesign does not sign text files, why not just have a mechanism to skip over the text file (printing a warning if you must) and allow electron-builder's code signing process to continue?