- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
Extension for Chrome
Chrome is resuming the transition to MV3 extensions. Chrome will begin disabling Manifest V2 extensions in pre-stable versions of Chrome (Dev, Canary, and Beta) as early as June 2024, in Chrome 127 and later.
Enterprises using the ExtensionManifestV2Availability policy to ensure the continued functioning of Manifest V2 extensions in their organization will have one additional year – until June 2025 – to migrate the Manifest V2 extensions in their organization. Browsers with the policy enabled will not be impacted by the rollout of the deprecation until that time.
See the full timeline for the Chrome migration to MV3 extensions here.
UiPathStudio.msi will stop working in Chrome. We highly recommend upgrading your UiPath Studio and Robot installations before this happens.
UiPathStudio.msi versions:
- 2022.10
- 2022.4
- 2021.10.8+
- 2020.10.14+
- 2019.10.9+
These versions can be downloaded from:
- Product Downloads in the UiPath Customer Portal.
- Resource Center in the UiPath Automation Cloud. To access Resource Center you need to login in your Automation Cloud Organization and click the Help button on the left navigation bar.
This extension helps you create browser automations in Google Chrome.
You can install this extension in multiple ways, as shown below:
- Open Studio.
- Navigate to Home > Tools > UiPath Extensions.
-
Select Chrome > Install. Choose one of the available methods from the drop-down:
- Group Policy Offline
- Group Policy Online
- All Users
- Current User
- Native Host Only
- Open Chrome and navigate to
chrome://extensions. - Enable the UiPath Web Automation extension if needed.
- Run the
UiPathStudio.msiinstaller. - Select an install mode, and then select Advanced Settings > Extensions > UiPath extension for Chrome. If Chrome is installed on your machine, the option is selected by default.
- Click Install. Studio setup continues while also installing the extension for Chrome.
The UiPath Extension for Chrome can also be installed from the command line of UiPathStudio.msi.
You can also install the UiPath Extension for Chrome by using Group Policies. This method silently installs the extension and enables it, without requiring user confirmation.
The Group Policy Offline installation method requires that the target machine is joined to a Microsoft Active Directory domain or Azure Active Directory.
It does not require access to the Chrome Web Store so it can be used in controlled environments for machines that have restricted Internet access.
UiPathStudio.msi uses this installation
method by default if its requirements are met.
You can also use this installation method by running from an elevated command prompt:
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chrome-policy-offline /silent&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chrome-policy-offline /silentIf your organization uses Group Policies for browser extension management then the following changes are also required to be made in your organization's group policy definition:
-
In the ExtensionInstallForceList policy, add the value:
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/ChromeExtension_SelfHosted/extension_manifest_chrome.xml -
In the NativeMessagingAllowList policy, add the value:
com.uipath.chromenativemsg_v2 - Set DeveloperToolsAvailability
Group Policy to the value
1(Allow usage of the Developer Tools) to enable the full extension functionality. For more information, please check the troubleshooting page.
.crx file at this location:
C:\Program
Files\UiPath\Studio\UiPath\BrowserExtension\uipath_extension_for_chrome_self_hosted_mv3.crx
https://clients2.google.com/service/update2/crx and
https://clients2.googleusercontent.com/crx).
UiPathStudio.msi
uses this installation method if its requirements are met and the machine is not joined to a
Microsoft Active Directory.
You can also use this installation method by running from an elevated command prompt:
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromepolicyglobal /silent&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromepolicyglobal /silentIf your organization uses Group Policies for browser extension management then the following changes are also required to be made in your organization's group policy definition:
-
In the ExtensionInstallForceList policy, add the value:
jfcmnbofjlffnejneillkgbniiidiigd;https://clients2.google.com/service/update2/crx -
In the NativeMessagingAllowList policy, add the value:
com.uipath.chromenativemsg_v2 - Set DeveloperToolsAvailability
Group Policy to the value
1(Allow usage of the Developer Tools) to enable the full extension functionality. For more information, please check the troubleshooting page.
The UiPath Extension for Chrome can be uninstalled by running from an elevated command prompt:
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromecleanup /silent&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromecleanup /silentYou can also uninstall by opening Studio, navigating to Home > Tools > UiPath Extensions, and selecting Chrome > Uninstall. The extension will be uninstalled with the same method used for the installation. This method is displayed in the disabled drop-down next to the Uninstall button.
The UiPath Extension for Chrome MV2 requires Chrome version 64 or greater.
The UiPath Extension for Chrome MV3 requires Chrome version 98 or greater.
When using one of the installation methods described above, the browser version will be checked and the extension with the appropriate format (MV2 or MV3) will be automatically installed.
UiPathStudio.msi 2022.4 the UiPath Extension for Chrome can be used to automate Chrome Apps.
Starting with UiPath version 2023.10, the UiPath Extension for Chrome supports automating multiple browser instances running with multiple user profiles at the same time.
For versions lower than 2023.10, the UiPath Extension for Chrome did not support automating multiple browser instances running with multiple user profiles at the same time. As such, browser automation required you to close all active instances of Chrome and restart the browser using a single user profile. Starting with version 2023.10 we can accommodate scenarios of multiple browser processes running under different browser profiles, such as the case when a specific application must run on a dedicated profile to isolate sensitive data from other applications.
UiPathStudio.msi v2023.10 or newer.
Opening the browser with a specific profile is now possible when using the Use Application/Browser activity. To specify a profile at browser start-up, you must append an argument to the browser command line. To do so, use the Arguments property in the Unified Application Target input section.
--profile-directory="profile_path".
profile_path is the relative path to the
User data folder path specified for that Use Application/Browser
activity. If the User data folder path isn't specified, then the profile path
is relative to the default user data directory
%LOCALAPPDATA%\Google\Chrome\User Data%. To find the profile
path, navigate to chrome://profile-internals/ and retrieve it from
the Profile path entry.
Your system administrator might have configured Group Policies that prevent the UiPath Extension for Chrome from working. To enable it, please follow the instructions from the Group Policies page.
For any other issues regarding the UiPath Extension for Chrome, please view the detailed troubleshooting page.
