Studio 2025.0.172-cloud.20749 - 7/30/2025
Community License
Attended, Automation Developer
Per-user Installation
Microsoft Windows 11 Pro 64-bit
8.0.15
Workflow : Data entry and acceptance with DoubleUI (UiPath Academy training) application
Source : Downloaded from UiPath Academy course Automation Developer Professional Training (v2023.10), module User Interface (UI) Automation with Modern Design in Studio exercise Part-2
Dependencies (2: System.* and UiAutomation.*) were up-to-date; performed tryouts with labeled as âstrictâ and âlowest applicable versionâ
Donât blame me, its almost impossible to be able to explain whatâs going in a shorter way; I would loose essential information, and yes, one might speculate in the wrong direction and respond with tips, I already tried!
Not that Iâm relatively new with UiPath Studio, but itâs the (stupid) researcher in me, who simply want to know; âwhat on earth is happening, here?â Tarifs? And, no,
itâs not Assistant who is hampering, or
disurbance of Windows notification,
I am not working in a RDP session, VM or other sandbox,
have tried the UseApplication property: open,
have toggled-on 'attended automation in project-settings (tab:general),
have tried as first activity inside the Do-sequence: Activate Window (from the Classic list), and yes,
I have tried (tweaked a lot) it in Service Mode (thatâs where the problem elevated!)
Anyway in short: in whatever input activity, the first in the Do-sequence of the âUse Applicationâ container, an input one (no matter if it was a NTypeInto or NClick) they both are able to detect the DoubleUI app, simply because the dialog could be targeted - option (I) in each of detection option menu - green boxes were seen and the dialog selectable and clickable, also using the UI explorer, the validate button turns green, re-indication and/or choosing another framework (default, AA, or UIA) also green boxes are visible and the dialog could always properly selected.
However, but trying to âcheckâ the âconnectionâ - through highlighting the target, or through hamburger-menu option-H or the icon on the UI explorer ribbon icon - then for frameworks default and AA nothing happens, no boxes no successful connection, and for UIA a red box is popping-up.
Alarm bells went off! Being a bit stubborn, running the workflow, as expected the first activity TypeInto sees its target > green box on the target input appear, but one way or the other, it ends up with an error saying: âcannot bring target to the foregroundâ, while the DoubleUI dialog is on the foreground.
Working on version UiPath Community 25 running on an up-to-date windows LT (one screen), checked with sysinternals - process explorer, if UiPath and DoubleUI are on the same session and integrity level; yes, they are running in the same session (value 1) and it says for both an integrity of âaverage mandatory levelâ, the only thing I was is different the DoubleUI isnât digitally signed. Is this the problem?
I started with this workflow on this same machine running UiPath version 24, in Service mode, because I have been working on Unattended processes in the past. With that laboratory setup, I could reach in this demo flow at least the third âNClickâ activity; meaning the two preceding TypeInto activities were passing by successfully. Trouble occurred on the third click activity; erroring saying. it canât bring application to the foreground. That was the starter of this search, from which I thought should easily be solved, however, I sank deeper and deeper into the culpritt. And yes, in service mode I have tried instead of the first NTypeInto a NClick and hooked that on the title of the dialog, anchored it properly, as well green boxes but something else inside that activity tells; nope, cannot bring it to the foreground.
Expecting with a little help of the smartest human-like-aliens available, they have let me tweaking a lot! Every time the NClick activity said: No, cannot bring to fore ground. No matter what kind of input mode Hardware events- or Use same as Application setting, every time the same answer. Donât tell me I should had used simulate, windows message or chromium, no those settings arenât usable because then activity itself already started complaining: cannot use it.
In the end, several aliens suggested, go back to black and try âUser Modeâ! Do stupid human, believe us, we know the best, 101% sure it will work; the 1% tarif will do the trick! trust us, do blindly follow us! Donât believe people on the form! Fool I was! No way! The 1% tarif time spent, turned out in 220% waisted precious time. Is that what using UiPath today is outh to achieve?
It turned out all âdigitally helpersâ today telling âfairy talesâ. I slept over, gambled, tried dices and took the blind way what could I do else through my LT out of the window? I gambled, trial error and followed tarif-pathway. It turned out, sorry Iâm saying, I really lost some trust in those electronic woohaaâs, even in UiPathâs Autopilot for Everyone. That tool was at least the most honest one in responsing to me; I donât what youâre are talking about.
I removed UiPath from LT, tried to clean windows registry from any remnant of UiPath, yes, I took precautions, I do have followed documentation how to (I think. may be Iâm too stubborn, I know a little bit what Iâm doing). Restart, re-installed UiPath newest version (v25), now in User mode, because according several of those electronic woohaaâs, their I would find the holy grail. Again, trying the same tweaks as I have done when running in Service Mode (yes, I have checked if the UiPath Robot was not running in User mode, yes it did not).
Currently, being in User mode, it became terribly more worse instead of a tiny little step forwards! Now I experience analogue behavior, now already on the first NTypeInto activity (the one which was working well in Service mode). Again, I do see green boxes, but highlighting is creating a red one (UIA framework, comparable behavior what I had seen running in Service mode on the third NClick activity). As expected, running it, yes, it does see the dialog (dialog visible on screen) but immediately argues âcannot bring target in the foregroundâ.
I am out of options!
effect!