robot
2021.10
false
- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET6 Projects Fail to Run
OUT OF SUPPORT
Robot User Guide
Last updated Nov 11, 2024
Enforced Package Signature Verification
After upgrading to Studio v2019.4 or above from an older version, some processes fail to execute. This is only applicable if package signature verification is enforced. Find out how to sign a package and how the Robot verifies a package signature.
Once the upgrade to Studio v2019.4 or above is done, the packages folder (
C:\Program Files (x86)\UiPath\Studio\Packages in versions prior to 2021.4 or C:\Program Files\UiPath\Studio\Packages starting with version 2021.4) gets populated with signed activities packages, while also keeping the unsigned versions.
For example, the
Packages folder contains both the Microsoft.Rest.ClientRuntime.2.3.10.nupkg (unsigned) and Microsoft.Rest.ClientRuntime.2.3.12.nupkg (signed) packages. When a process gets executed, the Robot uses the lowest applicable version to install the required package,
which in our case is Microsoft.Rest.ClientRuntime.2.3.10.nupkg (unsigned). If package signature verification is enforced, then the process execution fails. Otherwise, the process is executed
as expected.
There are a couple of approaches to the situation:
- Make sure all the packages used in your automation projects are signed.
-
Modify your processes so that they request the latest package version upon execution.
Note: If signature verification is NOT enforced, processes created with Studio prior to v2019.4 are still executed, regardless if they are signed or not.
