- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- 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-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- 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-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Properties
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-017 - Invalid parameter modifier
- 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
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Troubleshooting
- Trigger-based Attended Automation
- Object Repository
- The ScreenScrapeJavaSupport Tool
- 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 Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Studio testing
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Validation of large Windows-legacy projects takes longer than expected
Studio user guide
Starting with UiPath.UIAutomation.Activities version 24.10.0, Safari UI Automation support is available in preview. The extension for Safari lets you:
- Design UI automations in Studio Web within the Safari browser on macOS.
- Execute browser automations in Safari using a local macOS Robot, previously installed and connected to the Orchestrator.
- Start attended browser automations in Safari via the macOS Assistant.
To create and run such automations, you must install the UiPath Browser Automation extension for Safari.
You can start from Studio Web by adding any UI Automation activities. When accessing Studio Web from Safari, you are prompted to install the UiPath extension for Safari from the App Store. Follow the setup guide to configure the extension, then start designing your workflows for browser automation in Safari.
To create browser automations in Safari on machines running macOS, the minimum supported version is macOS 12.
Install
Install from UiPath Studio Web
-
In UiPath Automation Cloud™, access Studio Web.
-
Add a Use Browser activity to your project. You are prompted to install the UiPath extension for Safari.
-
Select the Install extension button.
-
The App Store opens with the UiPath Browser Automation extension.
-
Select Get to install the extension, and then Open it.
-
After you select Open, a configuration window appears.
-
Select Open Safari settings to access the Extensions window, where you can set the right permissions for the newly installed extension.
- Enable the UiPath Browser Automation extension in the left-side panel.
2. Select Always Allow on Every Website and confirm this choice.
3. If you intend to use private browsing, enable the Allow Private Browsing setting.
Result: A message informs you that the extension is now available.
Install from App Store
You can access the UiPath extension for Safari directly in the App Store and continue the installation process from step 4 of the previous section.
Install from UiPath Assistant
Installing the Safari extension from Studio Web or directly from the App Store also installs the Native Host component. This means that you can run automations from UiPath Assistant without the need for additional installation.
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.
Install Steps
-
Access UiPath Assistant.
-
Select the account icon.
-
Select Preferences.
-
Go to UiPath Extensions.
-
Select View on App Store for Safari.
-
Select Install.
-
Select Open.
-
Follow the steps required by the extension.
Result: The extension is installed and enabled in Safari.
Install using an MDM
To install via an MDM (mobile device management) application, the machine has to be enrolled to be managed. More details on how device management works on Apple machines can be found on this page: Device Management | Apple Developer Documentation.
Examples of MDMs include:
- Jamf
- Microsoft Intune
- Kandji
- MicroMDM (open-source)
This method relies on the new declarative management model to push configuration changes to the managed machine(s). The configuration for Safari extensions is detailed here: SafariExtensionSettings | Apple Developer Documentation.
Install from Terminal
The installation from Terminal is performed via UiPath.ExtensionControl.Portable.dll.
UiPath provides a tool for managing extension installation: UiPath.ExtensionControl.Portable.dll. This tool is distributed with UiPath Assistant, which also includes the extension application packaged as an archive.
This method updates the Safari configuration so that the extension is recognized as installed. The extension is installed for the current user only.
This method is not meant for production environments, as it relies on a mechanism that Apple might change in future updates. Use it only if no other alternative is available.
Prerequisites:
- All instances of Safari are closed.
Install Steps
-
Open a Terminal and run the following command:
dotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install safari peruserdotnet /Applications/UiPath\ Assistant.app/Contents/Extensions/UiPath.ExtensionControl.Portable.dll install safari peruser -
Start Safari to design and run automations.
Uninstall
Uninstall from Safari settings
-
Access Safari Settings.
-
Navigate to the Extensions tab.
-
Select the Uninstall button.
-
Select the Show in Finder button. This opens the Finder with the application selected.
-
Open the context menu for the UiPath for Safari application and select Move to the Bin.
If a pop-up message states the application cannot be deleted because it is in use:
-
Open Activity Monitor and search for UiPath Native Host for Safari.
-
Select the application, choose Stop, then select Quit.
-
Return to Finder and select Move to Bin again.
-
-
Enter your Mac credentials and then select OK to authorize this deletion.
Result: The extension is uninstalled. It is removed from the Safari extension bar and from the Safari Settings Extensions tab.
Accessibility configuration
To use the Hardware Events input mode, you must specifically grant UiPath Assistant access to your Mac using the Privacy & Security settings.
To do so, follow the steps below:
-
Select the Apple menu.
-
Select System Settings.
-
Select Privacy & Security in the left sidebar.
-
Go to Accessibility by selecting the arrow on the right-hand side.
-
Enable UiPath Assistant from the list. If you do not see the application, select + at the bottom of the list, search for UiPath Assistant, select the application, and choose Open. Mac credentials are requested for this change.
Result: UiPath Assistant is now authorized to use Hardware Events input mode in Safari automations.
Known limitations
Consider the following limitations when creating browser automations for Safari:
- The extension cannot access file URLs. This is a Safari limitation, as explained in this Apple Developer forum thread (Allow access to file URLs for web extensions).
- The extension does not support multiple profiles.