Error after update to 6.3.1 - Cannot read properties of undefined (reading 'toPlay')

Hi,

After updating to 6.3.1, my script could not open website as normal.
Error is : Cannot read properties of undefined (reading ‘toPlay’)
Sometimes, if I press Play Macro again, it could run as normal. But sometimes, it doesn’t work anything.

Attached image!

Please help me to fix this update!
Thanks!

Waiting @admin for support

Hi @tutmin thank you for reporting this error! I have some some questions:

  1. Do you have a test macro for us to recreate the error?

  2. If not:

  • Does my small test (see below) work ok for you, too?
  • Do the Demomacros run OK for you? Is there anything special about this macro or the website?

I used copyfish to extract the URL from the screenshot, and made a small test macro, but this one works fine:

{
  "Name": "t1",
  "CreationDate": "2021-12-16",
  "Commands": [
    {
      "Command": "open",
      "Target": "https://dktructuyen.moj.gov.vn/dtn_str/search/public/",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "click",
      "Target": "id=registration_number",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "type",
      "Target": "id=party",
      "Value": "on",
      "Description": ""
    },
    {
      "Command": "type",
      "Target": "id=individual_id",
      "Value": "222",
      "Description": ""
    },
    {
      "Command": "type",
      "Target": "id=captcha_search_public",
      "Value": "33",
      "Description": ""
    }
  ]
}

I am seeing the same error unless I add a pause right after the open. Please escalate the issue priority.

Thanks,
Dave

Hi @Dave - do you have a test case or screen video for us? Currently the challenge is to recreate this error.

Question:

  • Do you start the macro via command line, bookmark or just via the UI.Vision user interface?

  • Also, is this on windows, macOS or Linux? Is it a slow machine?

Does anyone have a reliable way to recreate this issue? I have seen it now, but only very rarely. That makes the issue hard to debug.

Just got the same issue after update. Even if i press macro to replay, it doesn’t work.
Same code does work in version 6.2.8 which I’m running on another mac.

here’s a screenshot

here’s the code:
{
“Name”: “CB”,
“CreationDate”: “2021-12-20”,
“Commands”: [
{
“Command”: “store”,
“Target”: “fast”,
“Value”: “!replayspeed”,
“Description”: “”
},
{
“Command”: “store”,
“Target”: “2”,
“Value”: “!timeout_wait”,
“Description”: “”
},
{
“Command”: “open”,
“Target”: “${!COL1}”,
“Value”: “${!csvReadLineNumber}”,
“Description”: “”
},

once the error happens, you need to close Chrome completely, then it works again.

Does the “toPlay” error happen always you to, or only sometimes?

Good question: if I press ‘play’ in right click macro or ‘play macro’ it provides the error. if rightclick and click “testsuite: play from here” it runs smooth. But I only tested this once.

update: force quite Chrome and I can not replicate the error. so fixed!

I experience the same problem. Happens always

@kelturon Please close all Chrome instances to fix the issue (for a while). Or of course downgrade to V6.2.8.

i have the same issue, how to downgrade to V 6.2.8

You can downgrade to v6.2.8 here: Archive - UI.Vision RPA Software

@admin the problem has resurfaced since the latest Chrome update. Now I have to force quit Chrome each time.

Figured out what caused this issue for me. Everything was working fine with the update until I uninstalled ui.vision from chrome and reinstalled it to get ride of all my old files. I boot ui.vision from a saved short cut (not opening through chrome) when I went to play any macro that was working fine before I reinstalled I would run into this error right away. If I booted up ui.vision through chrome instead of the shortcut it would work for a little while then stop.

Installing the previous version fixed this issue for me.

1 Like

This issue is solved with today’s V6.3.2 update. Happy New Year!

Hi @admin , since 6.3.2. I have to restart Chrome for every run/play. Now I get the error consistently. With 6.3.1 I only had to restart Chrome once and it would play for awhile. I’m going with @mattv solution so I’ll downgrade