Just to compare: I used desktop client 2.3.0rc1 (build 4) to upload the files.
On what upload method/version does the error occur for you guys?
The newer stable 2.3.1 was not offered to me through the client. I will install it now and see, if the error persists. If so, I will create a github issue.
Any additional informations could be helpful. Error occurs for me during image and video files upload, did not observe large files of different kinds (e.g. archives) so far. Some documents were also uploaded, but since they are very small, I cannot assure, that the error was caused by them.
Is this a problem you solved?
I’m a 12.0.1 stable version, but the same error occurred. It doesn’t occur frequently, but sometimes it appears in the log.
Undefined offset: 3 at /var/www/vhosts/NEXTCLOUD/apps/activity/lib/FilesHooks.php#620
I changed that manually in 12.0.0 and this fixed the problem for me. With 12.0.1 this should have been included.
If this is already applied, it would be great, if you could find out during what kind of (most likely) file uploads this occurs. Maybe there is another kind of invalid $path not yet excluded in the code.
At that time the user was mounting Nextcloud on Windows (WebDAV) and editing file with Excel application. Probably… Or user have opened a spreadsheet file using Collabora Online.
So the user didn’t use nextcloud desktop client? I could imagine some error with the temporary ms/libre/whatever office files. Those are by default excluded via desktop client, maybe via other webdav they cause issues.
We don’t use any Nextcloud client application by anyone. WebDAV errors often occurred in older versions, but now there are no errors related to WebDAV (in the log).
I also can confirm that this error persists in 12.0.1
We are only using the official client applications (Windows, Android and Apple). No direct access via WebDAV.
Sadly I can not reproduce the exact circumstances that triggered it. I only know that my father moved large amounts of files yesterday (10.000+) and I now have about 50 lines with this error in the logs.
Checked the file. Can confirm that line 141 looks exactly like this.
@rabbit27 please give as much information as possible, nc-, webserver-, php-, browser console errors, if occur and which kind of files you transfer by what method (client, webdav, …).