Extensão do Chrome no Mac

Essa extensão ajuda você a criar automações de navegador no Google Chrome no Mac.

Installation methods

The UiPath extension for Chrome can be installed in several ways, depending on how much user interaction is permitted.

Extensions can be installed either for a specific user or per machine (for all users). The only difference between these two installation types is the location of the configuration files.

Install type	Configuration files locations
Por usuário	~{userId}/Library/Application Support/Google/Chrome/External Extensions/ ~{userId}/Library/Application Support/Google/Chrome/NativeMessagingHosts/ Replace {userId} with the username of the user.
Por máquina	/Library/Application Support/Google/Chrome/External Extensions/ /Library/Google/Chrome/NativeMessagingHosts/

Instalar a partir do UiPath Assistant

Installation using UiPath Assistant requires only a few clicks, with no additional configuration, as long as UiPath Assistant is already installed. This method installs the latest extension version published to the Web Store for the current user only.

1. Acesse o UiPath Assistant.

2. Select the account icon.

3. Select Preferences.

4. Vá para UiPath Extensions.

5. Select Install for Google Chrome.

   

6. Select Enable Extension in the Google Chrome confirmation pop-up.

   

Result: The extension is installed and enabled.

Install from Terminal (via UiPath.ExtensionControl.Portable.dll)

UiPath provides a tool for managing extension installation: UiPath.ExtensionControl.Portable.dll. This tool comes with UiPath Assistant, along with the additional files required to run the extension: UiPath.BrowserBridge.dll and chrome_nmh_wrapper.sh.

Pré-requisitos:

• Always run the command using the UiPath.ExtensionControl.Portable.dll file from the /Applications directory, as macOS is sensitive when it comes to executing binaries from other locations.
• Before running the command, ensure one of the following:
  • Extract UiPath.Extensions.Portable.nupkg into the /Applications/UiPath Assistant.app/Contents/Extensions folder and run the commands from that location.
  • Update the chrome_nmh_wrapper.sh script by setting the DOTNET variable to the path of the dotnet executable on your machine.
• Close all Chrome windows before running the command.

Usuário atual

This method installs the extension only for the current user. It creates or updates the JSON configuration files used by Chrome to detect extensions. These files define the extension ID, update URL, and the path to the native messaging host.

Observação:

Replace {extensionId} with the ID of the extension. See Studio - List of extensions for Chrome for a list of IDs. The --ext-id={extensionId} part of the command can be omitted, and the latest WebStore published extension will be installed.

Install Steps

1. Abra um Terminal e execute o seguinte comando:

   dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome --ext-id={extenstionId}
   

2. Select Enable Extension in the Google Chrome confirmation pop-up.

   

Result: The extension is installed and enabled.

Todos os usuários

This method installs the extension for all users on the machine. It works similarly to the Current User method by creating or updating the JSON configuration files that Chrome uses to detect extensions. The difference lies in the file location: this method writes the configuration files to a system-wide location, whereas the Current User method writes them to a user-specific location.

Observação:

• sudo is needed to run this command, as it updates system configuration files.
• Replace {extensionId} with the ID of the extension. See Studio - List of extensions for Chrome for a list of IDs. The --ext-id={extensionId} part of the command can be omitted, and the latest WebStore published extension will be installed.

Install Steps

1. Abra um Terminal e execute o seguinte comando:

   sudo dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome --scope=machine --ext-id={extenstionId}
   

2. Select Enable Extension in the Google Chrome confirmation pop-up.

   

Result: The extension is installed and enabled.

Política de grupo on-line

This method doesn't require the manual step to enable the extension after Chrome is first started. This is because it relies on Configuration profiles deployed by MDM (Mobile Device Management) tools.

The Configuration profile sets the ExtensionInstallForcelist policy. This policy ensures that the extension is enabled and that it can't be disabled manually.

This procedure is similar to the Windows Group Policy Online installation method described here: Studio - Extension for Chrome.

To install a Configuration profile (a .mobileconfig file) an MDM application should be present on the machine, and the machine has to be enrolled to be managed.

Examples of MDMs include:

• Jamf
• Microsoft Intune
• Kandji
• MicroMDM (open-source)

If the device is enrolled in a MDM, ensure that the configuration is not overridden by the Configuration updates pushed via MDM. To achieve this, push the Configuration profile directly via MDM. It should have a content similar to the one below:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PayloadContent</key>
	<array>
		<dict>
			<!-- This policy ensures that the {extensionId} is enabled -->
			<key>ExtensionInstallForcelist</key>
			<array>
				<string>{extensionId};https://clients2.google.com/service/update2/crx</string>
			</array>

			<!-- The policies below are not mandatory, but they are useful in some systems, 
         depending on the already present configuration -->
         <!-- This policy enables the Developer mode in chrome://extensions -->
			<key>DeveloperToolsAvailability</key>
			<integer>1</integer>
			
			<key>BlockExternalExtensions</key>
			<false/>
			
			<key>ExtensionAllowedTypes</key>
			<array>
				<string>extension</string>
			</array>
			
			<key>NativeMessagingUserLevelHosts</key>
			<true/>
			
			<key>NativeMessagingAllowlist</key>
			<array>
				<string>com.uipath.portable_host</string>
			</array>
			
			<key>PayloadDisplayName</key>
			<string>Google Chrome</string>
			<key>PayloadIdentifier</key>
			<string>com.google.Chrome.2C2280F4-2955-49E9-8161-A599B9BB6685</string>
			<key>PayloadType</key>
			<string>com.google.Chrome</string>
			<key>PayloadUUID</key>
			<string>2C2280F4-2955-49E9-8161-A599B9BB6685</string>
			<key>PayloadVersion</key>
			<integer>1</integer>
		</dict>
	</array>
	<key>PayloadDisplayName</key>
	<string>UiPath Studio Web Automation Chrome Extension Installation</string>
	<key>PayloadIdentifier</key>
	<string>com.uipath.chrome.extension.A64BC628-4ECF-4A71-91D5-20D7C7475C38</string>
	<key>PayloadOrganization</key>
	<string>com.uipath</string>
	<key>PayloadScope</key>
	<string>System</string>
	<key>PayloadType</key>
	<string>Configuration</string>
	<key>PayloadUUID</key>
	<string>A64BC628-4ECF-4A71-91D5-20D7C7475C38</string>
	<key>PayloadVersion</key>
	<integer>1</integer>
	<key>TargetDeviceType</key>
	<integer>5</integer>
</dict>
</plist>

Observação:

• sudo is needed to run this command, as it updates system configuration files.
• Replace {extensionId} with the ID of the extension. See Studio - List of extensions for Chrome for a list of IDs. The --ext-id={extensionId} part of the command can be omitted, and the latest WebStore published extension will be installed.
• Using the bypolicy option automatically sets the scope to machine.
• The command can be issued with --scope=user instead of --scope=machine, with the effect that only the current user gets the extension installed and automatically enabled. Any other user will not get the extension installed.

If the device is not enrolled in a MDM, the UiPath.ExtensionControl.Portable.dll tool will write the configuration directly, tricking Chrome into considering the device managed and applying the policy. This ensures that no user input is needed to enable the extension.

Install Steps

A. MDM-enrolled machine:

1. Open a Terminal and run the following command. The bypolicy argument can be removed if the configuration pushed via MDM is set to override existing values.

   sudo dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome bypolicy --scope=machine --ext-id={extensionId}
   

2. Create a new .mobileconfig file to configure the required policies. The .mobileconfig file should have roughly the content described above.

3. Install the Configuration profile using the MDM provider.

4. Start Chrome.

5. Design and run automations.

Result: The extension is installed and enabled.

B. Not MDM-enrolled machine:

1. Abra um Terminal e execute o seguinte comando:

   sudo dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome bypolicy --scope=machine --ext-id={extensionId}
   

2. Design and run automations.

Result: The extension is installed and enabled.

Política de grupo off-line

UiPath.ExtensionControl.Portable.dll cannot be used to fully perform this install type, as it requires intervention (either on the local machine or from an administrator machine).

UiPath.ExtensionControl.Portable.dll provides support for updating the configuration files needed by the extension for its communication with the native host. Therefore, it can be used to install the extension per user or per machine, as previously shown, but additional steps are required to ensure the extension is installed and enabled.

The Configuration profile sets the ExtensionInstallForcelist policy. This policy ensures that the extension is enabled and that it can't be disabled manually.

This method:

• Lets you install any extension, whether published to WebStore or unpublished.
• Is useful in environments with restricted Internet access (where https://clients2.google.com/service/update2/crx cannot be accessed).
• Requires MDM-enrolled machines for unpublished extension installations, as Chrome restricts unpublished extension installations to MDM-enrolled machines only.

The Configuration profile should have roughly the following content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PayloadContent</key>
	<array>
		<dict>
			<!-- This policy ensures that the {extensionId} is enabled -->
			<key>ExtensionInstallForcelist</key>
			<array>
				<string>{extensionId}</string>
			</array>

			<!-- The policies below are not mandatory, but they are useful in some systems, 
         depending on the already present configuration -->
			<!-- This policy enables the Developer mode in chrome://extensions -->
			<key>DeveloperToolsAvailability</key>
			<integer>1</integer>
			
			<key>BlockExternalExtensions</key>
			<false/>
			
			<key>ExtensionAllowedTypes</key>
			<array>
				<string>extension</string>
			</array>
			
			<key>NativeMessagingUserLevelHosts</key>
			<true/>
			
			<key>NativeMessagingAllowlist</key>
			<array>
				<string>com.uipath.portable_host</string>
			</array>
			
			<key>PayloadDisplayName</key>
			<string>Google Chrome</string>
			<key>PayloadIdentifier</key>
			<string>com.google.Chrome.2C2280F4-2955-49E9-8161-A599B9BB6685</string>
			<key>PayloadType</key>
			<string>com.google.Chrome</string>
			<key>PayloadUUID</key>
			<string>2C2280F4-2955-49E9-8161-A599B9BB6685</string>
			<key>PayloadVersion</key>
			<integer>1</integer>
		</dict>
	</array>
	<key>PayloadDisplayName</key>
	<string>UiPath Studio Web Automation Chrome Extension Installation</string>
	<key>PayloadIdentifier</key>
	<string>com.uipath.chrome.extension.A64BC628-4ECF-4A71-91D5-20D7C7475C38</string>
	<key>PayloadOrganization</key>
	<string>com.uipath</string>
	<key>PayloadScope</key>
	<string>System</string>
	<key>PayloadType</key>
	<string>Configuration</string>
	<key>PayloadUUID</key>
	<string>A64BC628-4ECF-4A71-91D5-20D7C7475C38</string>
	<key>PayloadVersion</key>
	<integer>1</integer>
	<key>TargetDeviceType</key>
	<integer>5</integer>
</dict>
</plist>

The ExtensionInstallForcelist string has the following formats:

• {extensionId}
• {extensionId};{urlWithThePathToTheUpdateManifestXmlFile}

The {urlWithThePathToTheUpdateManifestXmlFile} value has to be replaced with an URL (https:// or file://) to the update manifest XML file. This file has the following content:

<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
	<app appid='{extensionId}'>
	<updatecheck
		codebase='{crxUrl}'
		version='{extensionVersion}' />
	</app>
</gupdate>

Observação:

• Replace {extensionId} with the ID of the extension.
• The {crxUrl} has to be replaced with the URL of the CRX (https:// - if the CRX is hosted on a server, or file:// - if the file is placed on the local machine).
• The {extensionVersion} has to be replaced with the version of the extension (something like 24.10.3).

Install Steps

Observação:

Steps 1 and 2 are performed on the administrator machine.

1. Create the Configuration profile as described above.

2. Push the profile using an MDM provider.

3. Install the native messaging host by opening a Terminal and running the following command:

   dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome native-messaging-host-only --scope=machine --ext-id={extensionId}
   

4. Start Chrome.

5. Design and run automations.

Result: The extension is installed and enabled.

Alternative install steps:

These steps can also be performed on the local machine, without intervention from an administrator. They require manual intervention and extra care.

1. Start Chrome.

2. Open chrome://extensions.

3. Enable Developer mode from the toggle placed in the top right of the page.

4. Drag and drop the CRX file to the page.

5. Select the Add extension button; Chrome will show a Safety Check related to the extension (this is because the extension is not published to the WebStore), but you can ignore it.

6. Quit Chrome.

7. Abra um Terminal e execute o seguinte comando:

   dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome --scope=machine --ext-id={extenstionId}
   

8. Install the Configuration profile that forces the installation of the extension. The device must be enrolled in an MDM. The Configuration can be installed manually or pushed from the MDM server. If the manual option is chosen, care should be taken that it doesn't override any profile values sent from the MDM server.

9. Start Chrome.

10. Design and run automations.

Result: The extension is installed and enabled.

This method relies on Configuration profiles deployed by MDM (Mobile Device Management) tools. The Configuration profile applies the ExtensionInstallForcelist policy, which ensures that the extension is automatically enabled and cannot be disabled by users.

This procedure is similar to the Windows Group Policy Offline installation method described here: Studio - Extension for Chrome.

Load Unpacked

UiPath.ExtensionControl.Portable.dll can be used to enable the Native Messaging Host for extensions installed via Load Unpacked. UiPath.ExtensionControl.Portable.dll provides support for updating the configuration files needed by the extension for its communication with the native host.

This method lets you install any extension (published to WebStore or unpublished).

It is useful in environments with restricted Internet access (where the WebStore download URL https://clients2.google.com/service/update2/crx can't be accessed), or for testing extensions that are not published to the WebStore.

Observação:

Use --ext-id=self-hosted to install the Self-Hosted extension.

Install Steps

1. Install the extension using Load Unpacked.

2. Install the native messaging host by opening a Terminal and running the following command:

   dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install chrome native-messaging-host-only --ext-id={extensionId}
   

3. Start Chrome.

4. Design and run automations.

Result: The extension is installed and enabled.

Desinstalar

Desinstalar a partir do UiPath Assistant

1. Acesse o UiPath Assistant.

2. Vá para UiPath Extensions.

3. Select Uninstall for Google Chrome.

   

Result: The extension is uninstalled.

Desinstalar a partir do Terminal

Você pode desinstalar a extensão para o usuário atual executando o seguinte comando:

dotnet UiPath.ExtensionControl.Portable.dll uninstall chrome extnmh peruser

Result: The extension is uninstalled.

Verificar o status

To check the status of the Chrome Extension, run the following command from Terminal:

dotnet UiPath.ExtensionControl.Portable.dll status chrome extnmh peruser --nmh-path=<nmh path>