This will also upgrade the Chrome extension, but if Chrome is running then the user will have to manually re-enable the extension.
The extension may become disabled if Studio is upgraded with UiPathStudio.msi while Chrome is running. The installation directly from the Chrome Web Store is not presented in the online doc because the extension should be installed either from Studio, or with the Studio Installer UiPathStudio.msi, or with SetupExtensions.exe, to ensure a correct installation of all the components. In fact, there are several Chrome extension versions, bundled with different Studio versions. The UiPath Chrome extension is present in the Chrome Web Store. Logs might reveal why the Chrome choses to disable the extention. If it’s overnight then the logs could get very large. It could be useful if the issue reproduces quickly. These command line flags can be passed in a workflow if Chrome is started with the Open Application or the Start Process activity. More info here: Chrome Browser debug logs - Chrome Enterprise and Education Help Chrome can be launched with the command line flags -enable-logging -v=1 and it will collect logs in a file %LocalAppData%\Google\Chrome\User Data\chrome_debug.log Starting with Studio 20.10, it should be automatically installed through policy if the conditions are met: internet access, admin rights, an enterprise licence of Studio.įor older versions of Studio or a community licence, the SetupExtensions tool can be used: About the SetupExtensions ToolĪs for the cause of this issue, this needs careful investigation.
One possible solution, if the machine has access to internet, is to install the Chrome extension with policy.
0 kommentar(er)
