Answered

Java UI Elements not recognized

(0) Share

Report

Posted on by ConnorR

I recently updated my PC's verson of PAD to 2.22.263.22202 and it looks to have broken the java integration.

I run an Unattended bot process which needs to click through and enter data in an old java application, but PAD is no longer able to recognise the specific buttons - instead only finding Panel & Window objects when I hover / click with the add UI Elements finder. This has only become an issue since I updated to this version.

So far, I have completed every step in this article: https://docs.microsoft.com/en-us/power-automate/desktop-flows/how-to/java

Everything looks to be correct per this article, and all the referenced files are in the correct place in my PC's directory.

To fix the issue, I've been able to reinstall an old version of Power Automate desktop which has repaired the functionality. I haven't seen any other articles about this so I was curious as to whether this is an isolated issue or if there's an existing BUG ticket open for this already?

A similar issue happened at the tail end of last year, but was subsequently resolved with the next update; https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Java-application-stopped-working-with-PAD/m-p/1317469#M7712

Categories:

Power Automate Desktop

I have the same question (0)

All responses (2)

Answers (1)

AscendDev 8 on at

Like (0)

Report

Little late, but I had the same problem

This article (below) got me working, specifically, the part about blockSWT, this was the only thing to get mine working

https://learn.microsoft.com/en-us/power-automate/desktop-flows/how-to/java?source=recommendations

Was this reply helpful? Yes No
Verified answer

ConnorR 11 on at

Like (1)

Report

For reference, I'm glad to say this is now resolved.
After speaking with a couple of the Microsoft Power Automate Support Engineers we managed to confirm that it was actually an issue with the update.
To give a very rudimentary understanding of the issue; we found it was due to the java application being launched off a remote server rather than locally. The previous versions (whether intentionally or not) would support java applications running from remote servers, but the update listed in my initial comment seemed to undo this.
A fix has since been released (2.24) which has resolved the issue for us.

Was this reply helpful? Yes No