Why do Runtime packages appear when opening a Test Automation Project? Why are Activities within the Test Automation Project not interactable, but replacing the activity fixes the issue? How can the Separate Runtime Dependencies setting be verified for a Test Automation Project? How can runtime packages be prevented from appearing after publishing a Test Automation Project?
Overview
Test Automation Projects in UiPath Studio handle package dependencies differently from standard automation projects. When the Separate Runtime Dependencies feature is enabled, packages are split into design-time and runtime components upon publishing. This causes runtime packages to appear when the published NUPKG is opened in Studio, and can prevent users from interacting with Activities as expected.
This article explains why this occurs, how to verify the current setting, and how to resolve the issue.
Prerequisites
Before following the steps below, confirm the following:
- The affected Test Automation Project is open in UiPath Studio
- The local project directory is accessible via File Explorer
- Notepad or Notepad++ is available for editing the design.json file
- Package management permissions are available for the project
Step 1 — Verify the Separate Runtime Dependencies Setting
- In Studio, click File Explorer on the Test Automation Project. This opens the local directory where the project files are stored.
- Open the .project folder.
- Open design.json using Notepad or Notepad++ (preferred for readability).
- Search for the key SeparateRuntimeDependencies.
- Check the value:
- If set to True — this is the cause of the issue. Proceed to Step 2.
- If set to False or the key is absent — this setting is not the cause. Contact UiPath Support for further investigation.
Step 2 — Disable Separate Runtime Dependencies
- In design.json, change the value of SeparateRuntimeDependencies from True to False.
- Save and close the file.
Note: This change only affects future publishes. The current package state in Studio must also be fixed (see Step 3), and the project must be republished for the change to fully take effect.
Step 3 — Restore Full Packages in Studio
Install Full (Design-Time) Packages via Manage Packages
The packages listed below are the standard default packages present in most Test Automation Projects. Additional packages may also be present depending on the specific project configuration — identify and install the full version of every runtime package found in the project.
Standard packages to install (versions will vary per project):
| Package Name | Notes |
UiPath.UIAutomation.Activities | Standard default package — version varies per project |
UiPath.System.Activities | Standard default package — version varies per project |
[Any additional full packages] | Install the full version of any other runtime package found in the project |
Remove Runtime-Only Packages
Remove all packages carrying the .Runtime suffix. The following are the standard runtime packages typically present, but the full list will depend on the specific project:
| Package Name | Notes |
UiPath.UIAutomation.Activities.Runtime | Standard default — remove if present |
UiPath.System.Activities.Runtime | Standard default — remove if present |
[Any additional .Runtime packages] | Remove all other packages with the .Runtime suffix |
Note: The exact package list and versions will vary per project. As a general rule — for every .Runtime package found, remove it and install the corresponding full package at the matching version. Do not upgrade or downgrade versions during this process unless instructed by UiPath Support.
Step 4 — Save, Restart, and Republish
- Save the project in Studio.
- Close UiPath Studio completely.
- Reopen Studio and reload the project file.
- Verify that only full packages (without the .Runtime suffix) appear under dependencies.
- Republish the project to Orchestrator or locally to apply the corrected design.json settings.
If the issue persists after following all steps above, contact UiPath Support and provide the design.json file, Diagnostic Tool Report, and the Studio version in use.