Hello, I am trying to apply ProxyConfiguration on the WebKit webview. I've tried HTTP and SOCKSv5 without authentication, and it proxies normally. However, after I set up username authenticate on the server side, then set username and password with applyCredential on the client side, it couldn't authenticate the connection. Logs on the server side show the client side says it doesn't support any authentication. So I have some questions about the authentication: Does the ProxyConfiguration support authentication now? Does applyCredential apply credentials on HTTP/HTTPS and SOCKSv5 proxy?

`shauryajetty@Shauryas-MBP ~ % brew -v install apple/apple/game-porting-toolkit Warning: apple/apple/game-porting-toolkit 1.0.2 is already installed, it's just not linked. To link this version, run: brew link game-porting-toolkit Error: /usr/local/opt/game-porting-toolkit is not a valid keg` how the heck do I fix this?? I am on macOS 14 dev beta 3, and my computer ran out of battery during the install (face palm) but then it stopped and I tried install Game Porting Toolkit and got this. I tried the command but nothing happened.

I am trying out the new ProxyConfiguration API for OHTTP and didn't get the expected result. I was using it with WKWebView. I have a relay test server that blocks requests to certain urls instead of forwarding them to the gateway. So for example if the user loads test-blocked.com in the web view they'd get an error, while test-allowed.com would be forwarded to the gateway and the website would be loaded. Now in my test using the code from the Ready, set, relay presentation the website would be loaded for both urls (blocked & allowed) and the relay was not hit at all. If I understand the ProxyConfiguration correctly allowFailover is set to false by default which means if anything is wrong (config or otherwise) no content should be loaded for any given url. Is that assumption correct? I tried using the URLSession example as well with the same result. Is the ProxyConfiguration API supposed to work in Beta 2? Are there any gotchas I have to look out for to make this work? Any help or pointers would be appreciated.

By creating a provisioning profile on the dashboard or let Xcode (14.3.1) do an automatic signing to obtain that profile, the Network Extensions contains now additional "relay" item, which is not available, when capabilities are added in the Xcode (tried on Xcode Beta 15.2 as well) The relay is visible though in the web inspector, when provisioning profile is created via developer dashboard That said, the provisioning profile file (.mobileprovision) has this: and in the raw XML: if I would try to manually modify XML entitlements in the Xcode by adding relay, the Signing and Capabilities page of the Xcode project does not reflect this change and eventually removes this additional code line, if I try to select a proper item, for instance DNS Proxy Is it a new Bug introduced recently? Is it that just Xcode "forgot" to get this update (in Beta as well). The problem is that old profiles stopped working as they do not contain relay