The documentation clearly states it doesn’t require this activity to be inside a “Use”. Another project I recently created does not have it inside one. Both projects are currently open in different UIPath instances, checking the same application state but only one is complaining. This makes no sense.
2 Likes
Bumping this since it appears for me as well to still be the case. Is this perhaps a case of using incompatible UiPath Studio versions and Activity package versions? If so, I’d like to know a reliable way to determine whether an Activity package version is incompatible with the version of UiPath Studio I’m running.
Update: It now works as intended outside “Use Application/Browser” activity when working with Studio 2023.10.4+ and UiPath.UIAutomation.Activities v23.10.11+
1 Like
Still can’t believe this has not been answered.
Having it inside the use app browser is creating an issue instead of resolving one. I do not want the app to open if it is not already open.
It now works as intended. See updated post above.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.