Nextcloud error copy - "Cannot read properties of undefined (reading 'error')"

[Ketter]

Hi

After the upgrade of nextcloud (current: Nextcloud Hub 8 (29.0.2)) I bump into “Cannot read properties of undefined (reading ‘error’)” while using the “COPY” function (I suspect the “MOVE” might cause issues too.
Did the actions manually and found no blocking issues.

I believe it was the butler with the "PUT"put-stick in the "API"celler that changed in v29 of Nextcloud… but I ain’t no Benoit Blanc

The input;

[
  {
    "path": "AA_UPLOAD/CLEAN/FILENAME21.pdf",
    "lastModified": "Fri, 07 Jun 2024 14:06:30 GMT",
    "contentLength": "42526",
    "contentType": "application/pdf",
    "type": "file",
    "eTag": "490a0a7f60516a009c4a4c0169561db7"
  }
]

Looks as expected, and the content (in binary form) is what it should be.

The output error however;

{
  "errorMessage": "Cannot read properties of undefined (reading 'error')",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "1.44.1 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "TypeError: Cannot read properties of undefined (reading 'error')",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:666:253",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1079:20"
    ]
  }
}

Information on your n8n setup

• n8n version: 1.44.1
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via : Docker version 26.0.2
• **Operating system: Ubuntu **

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Ketter]

This issue has been resolved in 1.44.2. (verified with docker release)

And I believe the resolution can be found here;

Error Handling Issue in HTTP Request Node during PUT Operation

Alaaf!