Latest UiPath System/UiAutomation activities Issues

[whitestar (Phyo)]

Hi,

Just want to confirm if it’s just me or not. I updated the project packages of System and UiAutomation to latest version (22.4.4 for UiAutomation and 22.4.2 for System).

Upon updating the packages. I can’t use some of the classic activates anymore in existing project. it’s unable to capture the correct selector.

My current studio version is 2021.10.4

Thank You

[supermanPunch (Arpan)]

@whitestar

I can’t use some of the classic activates anymore in existing project

@whitestar , This might be because of the Default Behaviour of the Studio to Enable Modern Design for New Projects.

However, we should be able to bring out the Classic Activities using the Filter Option in Activities Panel :

[whitestar (Phyo)]

Hi @supermanPunch ,

I already enabled everything same as snapshot provided.

Just that some of the existing classic activites Selector won’t work anymore with new version. Even after Revalidation of the activities. unsure if i need to update browser extension as well or not.

[supermanPunch (Arpan)]

@whitestar

existing classic activites Selector won’t work anymore with new version.

@whitestar , Could you explain as to what is not working ? If it is not being validated, Can you take a Copy of the Current Selector and Indicate the Element again and Check the Differences between the Previous and the Current Selector ?

[whitestar (Phyo)]

I am using both classic and modern activates in project.

Let’s say If I want to indicate element using Classic activity. it’s capturing as Modern in Ui Explore causing it to fail.

Hope it make sense.

[whitestar (Phyo)]

Another example would be if i downgrade the activities from 22.4.4 to 21.10.4 .

The project will give an error for some of the UI modern activites as invalid.

[whitestar (Phyo)]

I also found out the new version is not backward compatibility, unlike the previous version where I can downgrade anytime and still be able to use the activities not anymore with the new version.

Hi @loginerror, could you please confirm if it’s intended to do this way?

Thanks

[loginerror (Maciej Kuźmicz)]

Any chance it could relate to this recent change?

UiPath Chrome Manifest V3 Extension Released with 2022.4 Update

UiPath Chrome Manifest V3 Extension Released with 22.4 Update Context The adoption of Manifest V3 represents one of the biggest shifts in the Google Chrome extensions platform since it launched a decade ago. Extensions using Manifest V3 will enjoy enhancements in security, privacy, and performance. The new UiPath Chrome MV3 extension We’ve implemented a completely new extension following the Manifest V3 standard released by Google. This new extension can be installed from both Studio ->Tools…

@whitestar

I also found out the new version is not backward compatibility, unlike the previous version where I can downgrade anytime and still be able to use the activities not anymore with the new version.

It was always like that. Basically, new package versions know the history and can keep things compatible, and old package versions have no idea how to interpret new things from the future.

[whitestar (Phyo)]

Hi @loginerror

We are still using version 21.10.4 for our chrome extension . So it could be why some of the selector are not working anymore with older package version.

Before even if we downgrade the packages version we are still able to use the activities at least until version 2021.10 packages.

I will discuss together with technical support for this issue as well. Thank You

[Arifur.Rahman]

@loginerror i am using Studio ver22.4.4 and i am facing lot of freezing issue with the studio when i am trying to edit the sector field or while debuging the file. any suggestion.