Connection Refused error opening native apps
Problem
I receive the error: “Connection refused…” when attempting to open a native app using Cycle.
Solution
The “Connection refused...” error occurs when there is an issue with the WinAppDriver Cycle is attempting to use.
The following guide walks through how to download, install, and configure your system to use the WinAppDriver with Cycle:
How To Configure Your Computer to use Cycle's Native App Steps
Be sure to properly set the WinAppDriver location within Cycle’s Project Settings and to enable Developer Mode in Windows settings.
If this does not resolve the error Submit a Request to the Customer Care team.
Related Articles
How To Find Windows AppID for Native App Steps (unable to create new remote session)
Windows applications built using the Universal Windows Platform (UWP) API require Cycle to open the application using the AppID of the application rather than than specifying the executable application as needed when opening Classic Windows (Win32) ...
How To Decide When to Use Native App Steps
Beginning with Cycle 2.4, Cycle now has the ability to interact with native Windows applications by using the WinAppDriver (WAD). These new native app steps allow Cycle to interact with Windows applications without relying on desktop steps that are ...
How to Use xPath With Native App Steps
Native app steps and xPath Cycle native app steps (using WinAppDriver) allow for the use of several object locator types to identify objects within the app. Whenever possible, it is best to identify application objects using the WinAppDriver ...
How To Configure Your Computer to use Cycle's Native App Steps
Beginning with version 2.4, Cycle adds a new set of steps designed for interacting with native applications on your computer in specifically targeted ways. In order to use these steps, you will need to take the following steps on your machine: Step ...
How to use Inspect.exe and Locator Types with Native Apps
To use Cycle native app steps, it is recommended that Window’s Inspect.exe is used to identify app Object Identifiers. It is recommended to use Inspect.exe with multiple monitors. If you have not downloaded and installed Inspect.exe, follow the ...