- 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-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
- Variables
- Arguments
- Imported Namespaces
- 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
- Troubleshooting
Troubleshooting
This topic presents the most frequent reasons why the UiPath Extension for Firefox might not work properly, and how to solve these issues.
Description
Mozilla introduced an extension signing verification algorithm in Firefox, which disables add-ons for Firefox version 65.0 and lower. As such, if you install the UiPath Extension for Firefox on the browser version 65.0 or lower, the following error message is displayed:
This add-on could not be installed because it appears to be corrupt.
Solution 1
Update Firefox to version v66.0.4 or higher.
Solution 2
Starting with Studio 2020.8, the Firefox extension is newly signed and it should be properly installed on older versions of the Firefox browser.
Check if the UiPath Extension for Firefox is installed and enabled:
- In Mozilla Firefox, go to about:addons > Extensions.
- If the extension is not present, install it as explained here.
- Make sure the UiPath Extension is updated to the latest version.
To prevent possible issues:
- In Mozilla Firefox, go to about:addons > Extensions.
- Open Task Manager or Process Explorer.
- Check if the
ChromeNativeMessaging.exeprocess is running.Note: A separateChromeNativeMessaginginstance is running for the Chrome extension, so you need to close Google Chrome when performing this check.
ChromeNativeMessaging is not running:
- In Mozilla Firefox, go to about:addons > Extensions.
- Remove the UiPath extension manually by clicking the Remove button.
- Reinstall it as explained here.
In case the above information did not solve your issue, you can try getting additional information by viewing traces and analyzing the errors thrown by the UiPath extension. The following are types of traces you can collect and analyze:
For the general extension traces in Mozilla Firefox:
Go to Open menu > Web Developer > Browser Console (Ctrl+Shift+J). The Browser Console is displayed. All the errors generated by the extension are displayed here.
For traces generated by the web page you want to automate:
Go to Open menu> Web Developer > Web Console (Ctrl+Shift+K). The Web Console is displayed. All the errors for the current web page are displayed here.
For full traces, (not only errors) do the following:
- Open the Registry Editor.
- Navigate to the
HKEY_CURRENT_USER\SOFTWARE\UiPathkey. - Double-click the WebExtensionTrace REG_DWORD value. The Edit DWORD Value window is displayed.
- In the Value Data field, change the value to 1, and click OK. The value is saved.
Note: If the
WebExtensionTraceREG_DWORD value does not exist, you have to create it, by right-clicking the right panel, selecting New > DWORD (32-bit) Value, and providing the values mentioned above.
Check if there is some data missing in the Registry Editor:
- Open the Registry Editor.
- Navigate to the
HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts\com.uipath.chromenativemsgkey. - Open the
(Default)REG_SZ value. The Edit String window is displayed and should contain a path similar toC:\Users\YOUR_USER_NAME\AppData\Local\UiPath\uipath-ff.json. - Open the .json file at the path found above with a text editor, such as Notepad++.
- Check that the path property correctly points to where
ChromeNativeMessaging.exeis located, similar toC:\Program Files (x86)\UiPath Studio\UiPath\BrowserExtension\ChromeNativeMessaging.exe.
