Why does my automations works perfectly in Uipath Studio but can't even do one click on Assistant?

Hello,

I’ve been utilizing UiPath to automate tests on my Java application for months, investing significant time and effort into creating these processes. Initially, I executed them directly from UiPath Studio. However, upon discovering the assistant, I decided to transition to it due to its purported ease of use and the capability to run tests regularly and automatically.

Unfortunately, none of my six .xaml files are functioning properly with the assistant. They fail to initiate altogether.

For instance, one of the scripts is designed to install my application using a CMD prompt, but it doesn’t even attempt to open the CMD window. Instead, it simply remains idle, citing a failure to locate the UI element.

Similarly, another script, which simply clicks a button within my application, fails to execute properly in the assistant. Again, it’s unable to identify the UI element, whereas UiPath Studio handles the task flawlessly.

It’s baffling how a debugging tool can behave so differently from the software it’s meant to support and debug.

Before you ask, yes, I’ve ensured that both applications are up to date.

I’m frustrated that all the work I’ve put into this software seems to be futile, and now I’m faced with the prospect of redoing everything and constantly testing it in the assistant, fearing it might not work.

How are we expected to use this software effectively in real-world scenarios if it fails to perform reliably in such basic tasks?

Thanks for any advice that could help.

Best regards…

Hi @Anthony_Dardenne,

Are you using orchestrator assets to set the path of your application? Or any other variable in your selectors that is dependent on assets?

I’ve faced similar issues when publishing packages to Orchestrator and used a different folder, so make sure to publish properly if you are using Orchestrator: Studio - About Publishing Automation Projects

If possible, share with us one of the UI Selectors that is causing issues and the steps you are following to use Assistant.

Juan P.

Hi Anthony_Dardenne,
Please go to the properties panel for the desired activity (Activity that is not working properly) and
change the Targetin methods to Strict selector and Input mode to Window Message.

Cheers!

Hello and thank you for your prompt responses.

@juan.porras1, I appreciate the guide you provided, and i read it, but I don’t believe the issue lies with publishing, as I do receive the new version on the Assistant upon publishing. Also, I’m not utilizing Orchestrator’s assets. The primary issue arises during the application installation when opening the CMD, as it simply skips it:

Subsequently, I attempted manual installation and experimented with another script that interacts with the application itself. However, it crashes as well, albeit with a different error this time, indicating that it cannot find the “java*.exe” application. I then searched for it in UiPath Studio, and each time I click on an element within my Java application, the “java*.exe” appears in the selector, essentially everywhere. However, why does it function in debug mode? Also, this “java*.exe” stems from my usage of the app recorder.


UiPath.UIAutomationNext.Exceptions.UiAutomationException: No open windows found for 'java*.exe'. Please check if the application is running. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x800402ff at UiPath.UiSystemClass.StartInteractiveApplication(String bstrSelector, String bstrCommand, String bstrArguments, Int32 timeoutMs, StartApplicationFlags flags)
at UiPath.UIAutomationNext.Services.UiSystemService.<>c__DisplayClass16_1.<StartInteractiveApplication>b__2()
at UiPath.UIAutomationNext.Services.DriverServiceCore.WrapCom[T](Func`1 toExecute)
--- End of inner exception stack trace ---

@jose.ordonez1, I appreciate your suggestion, but the entire script is embedded within this application. If I alter this, I encounter numerous errors with clicks and Type Into activities.

Edit: I forgot to mention that the debugging and running in the Assistant are on the same computer with the same user.

1 Like

Looks like the CMD is no being opened before the execution. Make sure to set the the Open property to True

If possible, share the entire selector code with us:

Juan P.

Thanks for your help, i’m not really what did it, but i made it works… I really don’t know what was going on but hey, it does works now so thank you to both of you guys.

Best regards

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.