Hi team,
Since Google Chrome moved to Manifest V3, UI.Vision’s proxy switching has become unreliable with authenticated proxies (ip:port:username:password).
What happens
When Chrome shows the proxy authentication popup and I enter the user/pass, Chrome seems to “lock” onto that proxy. From that point on, any proxy changes sent by UI.Vision (e.g., setProxy | http//xxxxx:9999 | user,password ) are ignored by the browser. It keeps using the first authenticated proxy for the rest of the session.
Do you have any solution ?
Plus, when using the command setProxy, the ui vision logo doesnt turn red like it used to.
Thanks