How to not update Studio to latest version? 2018.1.0 issues

This happens when you first receive that warning message, after opening the xaml?

  1. Yes I get the image below whenever I open a project

  2. Every activity seems to have the issue, you no longer see the value of the property field you just see "Enter a VB Expression. You must click on the ellipses button to see the value of the property.

  3. UiPath Platform is not installed on the same machine, these are just instances of studio installed on developers local machines.

  4. Also the location of UiRobot.exe moved…I used to have a shortcut in my start menu since the UiRobot doesn’t start automatically so I could start it manually and since updating to 2018.1 that is no longer the location of UiRobot.exe it apparently lives inside the 18.1.0 folder

1 Like

Are you connected to Orchestrator while opening the workflow and seeig this error?

@Gabriel_Tatu yes it happens when the warning null error message appears when opeing the xaml.

Also for 1. I get the warning null error message every time I open the xaml. Both on new and old xaml projects. one I created 3 months ago, one I created yesterday, and one I created today. I get the message on all 3 of the xaml projects

Yes UiRobot is connected to Orchestrator

If you are connected to Orchestrator, disconnect and try again. Its a known issue that will be fixed in the next update, in a few days. You can also avoid this by not using double click on the xaml file to start it, and Open it from Studio
As for the Robot shortcut, you had a robot shortcut in Start menu, added by default? Beside the Studio one?

Disconnecting a reconnecting to orchestrator didn’t change anything…

Opening XAMLs from studio does fix the workflow designer issue I didn’t receive that this time…

As far as the issue with the properties pane I am still experiencing that after disconnecting and reconnecting to Orchestrator.

The shortcut to the Robot I created manually by right clicked on the UiRobot.exe icon and saying create shortcut and pasting that shortcut in my start menu so I didn’t have to navigate to the folder containing the icon to manually start Robot. However when Studio updated to 2018 the location of that moved so I had to do it again.

For the shortcut, yes it is normal to re-create it as the old one pointed to the old robot in 2017.1, so now you ll have to point to the new 2018.1 robot.
I m trying to understand now why you can’t edit the properties panel, we did not experience this problem so far.

Can you disconect from orchestrator, restart Studio (while still disconected) and see if you still see the issue?
Then reconnect again, and check again, please.

I think I figured out the properties panel bug…

So when you open a XAML from Studio I don’t receive the Workflow Designer error and the properties panel seems to be functioning fine. When I double click on a XAML from windows and let that open Studio then I receive the Workflow Designer error and have issues with the properties panel.

Yes, this is the bug. We will fix it soon, sorry for the trouble.
All your workflows will work now without issues.
Also i would suggest updating the core activities to latest version.

@Gabriel_Tatu
I also noticed that UiPath Explorer is constantly freezing and then proceeds to crash UiPath Studio.
I am trying to get the selector for a particular element, but this due to studio crashing this has become a daunting task.

On IE?

@cvent978 I just noticed yesterday the same with the properties panel, then I figured out that I should click the (…) button

other problem that I had noticed just now is when my workflow do an ocr activity is not working as always, I spend lot of time trying to configure the correct properties to have the perfect or almost perfect ocr working in citrix and now I’m having some troubles with that, I guess that is for the new version that I didn’t notice the update until now that I’m reading these issues.

What OS are you using for citrix automation? You may need a windows update.

my OS is windows 10 pro and I just checked and all the updates are ok.

another one, before, I never got this error when I want to send an email

The remote certificate is invalid according to the validation procedure.

What I should do here?

  1. What errors are you getting with the citrix automation? Which activities fail or whats happening exactly?
  2. You send email with what activity and where?

@Gabriel_Tatu

  1. I’m getting wrong data with ocr activities than I got good before.
    2 I just did a single test that was working fine before the new version …and now I got this error. image

what ocr activity are you using exactly? it is very important to know this

the second error seems to be related to the smtp server where you are trying to send an email, 18.1 update does not bring new mail activities automatically, those you install it yourself.