I got that error message when I’m trying to run a saved macro. This step is about uploading a picture
Hi! Can you please paste a test macro here that triggers the issue? (the shorter, the better)
{
"CreationDate": "2018-11-5",
"Commands": [
{
"Command": "open",
"Target": "https://us.letgo.com/en",
"Value": ""
},
{
"Command": "click",
"Target": "//*[@id=\"app\"]/div/div[1]/header/div/div[3]/button/span",
"Value": ""
},
{
"Command": "click",
"Target": "name=dropzone-input",
"Value": ""
},
{
"Command": "type",
"Target": "name=dropzone-input",
"Value": "C:\\pic.jpg"
},
{
"Command": "click",
"Target": "id=price-undefined-objectObject-53089",
"Value": ""
},
{
"Command": "type",
"Target": "id=price-undefined-objectObject-53089",
"Value": "190"
},
{
"Command": "click",
"Target": "//*[@id=\"dialog\"]/div/section/form/div/div[3]/div[4]/button/span",
"Value": ""
},
{
"Command": "click",
"Target": "//*[@id=\"dialog\"]/div/section/div/button[1]/span",
"Value": ""
},
{
"Command": "click",
"Target": "id=name-undefined-objectObject-42280",
"Value": ""
},
{
"Command": "type",
"Target": "id=name-undefined-objectObject-42280",
"Value": "Recliner"
},
{
"Command": "click",
"Target": "id=description-undefined-objectObject-14038",
"Value": ""
},
{
"Command": "click",
"Target": "id=description-undefined-objectObject-14038",
"Value": ""
},
{
"Command": "type",
"Target": "id=description-undefined-objectObject-14038",
"Value": "That's a brand new recliner you will like "
},
{
"Command": "click",
"Target": "name=category",
"Value": ""
},
{
"Command": "select",
"Target": "name=category",
"Value": "label=Home and Garden"
},
{
"Command": "click",
"Target": "name=category",
"Value": ""
},
{
"Command": "click",
"Target": "//*[@id=\"dialog\"]/div/section/div/div[2]/div[2]/div/button/span",
"Value": ""
}
]
}
I am getting same error when uploading image.
@uiuser Do you have a test macro for us?
https://picsart.com/create/editor?category=uploads
upload image to this url
@uiuser thanks for reporting this issue. I confirmed it and we will fix it asap.
The issue is fixed in V9.2.6. Thank you for reporting the issue!