Erros após atualização para versão 9.3.0

A versão 9.3.0 apresentou alguns problemas. Não está parando nos breakpoints e o foreach não está reconhecendo os arrays para executar o bloco. Além disso, alguns blocos estão sendo atropelados no processo, causando falhas em condicionais e a não espera pelo carregamento dos elementos na tela do navegador. Os blocos de clique e seleção de XPath também costumam apresentar dificuldades. Para contornar isso, sempre executo as ações e seleções usando executeScript e a solução apresentada no forum para usar com command: Store | target: FASTV1 | value: !replayspeed como solução de contorno. Para iterar num array, preciso utilizar o times, como alternativa ao foreach. Espero que esses bugs sejam corrigidos na nova versão o mais breve possível, pois a ferramenta é muito útil e tem uma boa performance.

Recentemente, ao rodar a macro, o código está quebrando no comando executeScript que segue abaixo:

[error]
Line 72: ipcPromise: onAsk timeout 3000 for cmd “PANEL_CALL_PLAY_TAB”, args {“ipcTimeout”:100,“ipcNoLaterThan”:3455622058638,“payload”:{“command”:“SET_STATUS”,“args”:{“status”:“PLAYING”}}}

JSON:

{
      "Command": "executeScript",
      "Target": "function getCurrentDateTime() {\n    var now = new Date();\n    var year = now.getFullYear();\n    var month = String(now.getMonth() + 1).padStart(2, '0');\n    var day = String(now.getDate()).padStart(2, '0');\n    var hours = String(now.getHours()).padStart(2, '0');\n    var minutes = String(now.getMinutes()).padStart(2, '0');\n    var seconds = String(now.getSeconds()).padStart(2, '0');\n\n    return year + month + day + hours + minutes + seconds;\n}\n\nconst dateTime = getCurrentDateTime().toString();\nreturn dateTime;",
      "Value": "dateTime",
      "Description": ""
}

I’m having the same problem here.

English version:

Version 9.3.0 had some problems. It is not stopping at breakpoints and foreach is not recognizing the arrays to execute the block. Furthermore, some blocks are being run over in the process, causing conditional failures and not waiting for elements to load on the browser screen. XPath’s click and select blocks also tend to present difficulties. To get around this, I always execute actions and selections using executeScript and the solution presented on the forum for use with command: Store | target: FASTV1 | value: !replayspeed as a workaround. To iterate over an array, I need to use times, as an alternative to foreach. I hope these bugs are fixed in the new version as soon as possible, as the tool is very useful and has good performance.

Recently, when running the macro, the code is breaking in the executeScript command below:

  1. Breakpoints → known issue, will be fixed asap

  2. For…each loop. Do you have a test case for me? I tested with the DemoCsvReadArray macro that ships with Ui.Vision, and it works fine.

  3. “Furthermore, some blocks are being run over in the process,…” → Do you have a test case for that? We are not aware of such an issue (yet).

  4. executeScript/PANEL_CALL_PLAY_TAB error - your command does not work for me, even on 9.2.9. I get a syntax error, some ] missing. Maybe this is a copy and paste issue. Can you please post a complete, small macro with the command inside?

@PhellipeSantos - What issue(s) do you see?

@admin admin, this is the error. As a result, the Macro stops, but there is no error. it freezes and nothing else happens.

  • [error][ignored]

Line 17: ipcPromise: onAsk timeout 5000 for cmd “PANEL_CALL_PLAY_TAB”, args {“ipcTimeout”:100,“ipcNoLaterThan”:3455742060918,“payload”:{“command”:“RUN_COMMAND”,“args”:{“command”:{“cmd”:“executeScript”,“target”:“return document.evaluate(‘//*[@id="paginationItemCountItemdiv_listar"]’, window.document, null, XPathResult.FIRST_ORDERED_NODE_TYPE, null).singleNodeValue != null;”,“value”:“elementExists”,“description”:“”,“extra”:{“playHighlightElements”:true,“playScrollElementsIntoView”:true,“timeoutPageLoad”:120,“timeoutElement”:0,“timeoutDownload”:60,“timeoutDownloadStart”:10,“lastCommandOk”:false,“errorIgnore”:true,“waitForVisible”:false,“superFast”:true,“retryInfo”:{“retryCount”:0}}}}}}

Hi, do you have a small macro that I can run that shows the PANEL_CALL_PLAY_TAB error? Because so far, I can not recreate it here.

1. Excelente

2. Tentei simular o erro no script abaixo. Utilizei o comando executeScript para retornar um array mas o retorno vira uma string nas variáveis internas.

Macro:

{
  "Name": "teste2",
  "CreationDate": "2024-10-2",
  "Commands": [
    {
      "Command": "executeScript",
      "Target": "return [\"a\", \"b\", \"c\", \"d\"]",
      "Value": "myArray",
      "Description": ""
    },
    {
      "Command": "forEach",
      "Target": "myArray",
      "Value": "item",
      "Description": ""
    },
    {
      "Command": "echo",
      "Target": "${item}",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "end",
      "Target": "",
      "Value": "",
      "Description": ""
    }
  ]
}


3. Simulei o comportamento utilizando o length de um array, que mesmo estando vazio, entrou na estrutura condicional.

Macro:

{
  "Name": "teste1",
  "CreationDate": "2024-10-2",
  "Commands": [
    {
      "Command": "executeScript",
      "Target": "return []",
      "Value": "myArray",
      "Description": ""
    },
    {
      "Command": "if",
      "Target": "${myArray}.length > 0",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "echo",
      "Target": "${myArray}.length",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "forEach",
      "Target": "myArray",
      "Value": "item",
      "Description": ""
    },
    {
      "Command": "echo",
      "Target": "${item}",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "end",
      "Target": "",
      "Value": "",
      "Description": ""
    },
    {
      "Command": "end",
      "Target": "",
      "Value": "",
      "Description": ""
    }
  ]
}

4. Trata-se de um problema intermitente relacionado ao comando executeScript.

Outra observação: A versão 9.3.0 não apresenta a cor verde nos blocos executados com sucesso sem utilizar o comando: store | FASTV1 | !replayspeed.

no, my code is extensive and for a private website. However, the error occurs when the macro is running and the site crashes. Sometimes there is a DOM error and sometimes this giant executeScript error.