Same problem here since the update to NC25. Some new infos? Only thing i can add: If you add new users they have the normal access to their files, but existing users befor the update don’t have the file/folder access
Same problem since I upgraded yesterday to version 25 - had been running perfectly for several years before that. It looks like I have this problem with the Windows desktop client only. The Android client and the web interface still work.
As the error message suggests this seems to be a type error. So to find a possible cause for this error I followed the traceback down to
/var/www/nextcloud/apps/dav/lib/Connector/Sabre/FilesPlugin.php - line 356:
That is:
$propFind->handle(self::SIZE_PROPERTYNAME, function () use ($node): ?int {
return $node->getSize();
});
Here, somewhat simplified, Nextcloud seems to request the size of an object and expects this property as an integer value while getSize() returns a float.
Consequently I changed the expectation from ?int to ?float just to see what happens… Reloaded the tab in Firefox—et voilá: my home directory is available again. Maybe these hints can help.
Please note, that I didn’t do any deeper investigation (,yet) so maybe there are side effects which don’t jump up on a quick glance: let’s see, what the developers work out 
24 Likes
Thanks alot! Works like a charm!
btw.
Unavailable display of files in the web interface and unable to synchronise since nc25 update appears to be the same issue.
1 Like
This is the response from the developers: [Bug]: TypeError: Return value of OCA\DAV\Connector\Sabre\FilesPlugin::OCA\DAV\Connector\Sabre\{closure}() must be of the type int or null, float returned · Issue #34674 · nextcloud/server · GitHub
Sadly I cant upgrade to 64 bit for other reasons.
Thanks for the temporary fix anyways
1 Like
Thanks for the workaround, I changed the file in my docker volume and I can now access my files again. I am looking into upgrading to 64bit anyway so that will hopefully fix long term.
As a slight aside:
The official line on the System Requirements page (System requirements — Nextcloud latest Administration Manual latest documentation) is:
CPU Architecture and OS
A 64bit CPU and 64bit OS is required for Nextcloud to run well.
I am not sure about a fresh build but to me this defect means that nextcloud doesn’t run at all let alone well.
I think either the supported OS pages need updating to state that 64bit is required or this defect needs fixing.
What does anyone else think?
Update: I see there was another update on the defect ticket saying that it was an unintentional change to break 32bit versions. I’ve added a comment on there that the official System Requirements should be updated
It looks like the issue with automatic int=>float conversion that previously existed on trashbin with >2 GiB data inside (of was it >2 GiB individual file size) now happens in the files app as well.
Also desktop client sync is affected for the same reason.
64-bit support was formally dropped due to the trashbin error, and also e.g. that >2 GiB couldn’t be downloaded via web interface on 32-bit systems, but those issues were acceptable for many 32-bit system users, including me. But the core functionality broken now is a real problem.
It wasn’t really clever to do this change while allowing 32-bit clients to upgrade without warning. A wave of broken instances (which hopefully have a backup or find this workaround for the time being) and related reports can be expected. EDIT: Was no intention, culprit seems to be a removed workaround in 3rdparty sabre submodule: Remove 4GB file size workaround for 32bit OS / Stream Videos on IOS by schoetju · Pull Request #184 · sabre-io/http · GitHub
1 Like
We didnt plan to actively remove 32-bit compatibility but it seems like we did for 25 without knowing as we do not test against 32-bit which is why we removed 32-bit support in the first place.
1 Like
Thanks a lot!
For those who like me are using the docker version on Raspberry Pi 32 bits, it’s not that easy to fix because there is no vi nor nano in the image and you cannot install it directly. I followed this path:
- docker exec -it nextcloud bash # change nextcloud to the name of your image
- apt-get update && apt-get upgrade
- apt-get install nano
- change the code as advised by Kay21 using nano:
nano apps/dav/lib/Connector/Sabre/FilesPlugin.php
For me the line to be changed was 354, not 356…
I had the same same problem. After updating to Nextcloud 25 in a Raspberry pi 4!!
This help me in a incredible way!!!
Thank you very much! @Kai21
Thanks a lot!!!
I had the same problem on raspberry 4B, and was bothered by it for a whole day!
Your solution is magical.
Many thanks! It did the trick for me as well 
Thanks! It Works
Thank you for this workround - it was driving me crazy. Brilliant.
Just wanted to say thank you and this is a great solution!
Work at all!!
Saved my evening, thanks a lot mate.
NC v25.0.2 will already contain that fix ([stable25] fix NC25 for 32-bit by szaimen · Pull Request #34905 · nextcloud/server · GitHub), now it’s time for migration planning to run NC on a 64 bit base to be future proof again.
That workaround bought some time. Migration has to happen until October 2023 according to Maintenance and Release Schedule · nextcloud/server Wiki · GitHub when support for NC v25 ends (the last major release series supporting NO working with 32 bit platforms… somehow, most of the time, if lucky).
The issue is apparently fixed in Nextcloud 25.0.2
Hello everybody, I just updated today to NC 25.0.2 (php8.1) and the issue is still happening for me: I can’t access my root folder in files.
I check the file mentioned in the solution marked above but even if this workaround is implemented, the problem persists for me.
EDIT: I can’t access the root folder via the we interface, as said above, but the synchronization of all files work when using the desktop client (created a file test.txt in a pc in the nextcloud/ root folder and it showed up in my other pc)
I can also access it in the android client.
Might be related to this issue? Because I can’t load the active users tab in the admin’s user settings
Hi everyone, an update on this.
A simple workaround for NC25.0.2 based on this commit that works for me: I gave unlimited storage quota to all users that have more than 4GB previously (I guess it also works if you give them less than 4GB but did not try it myself).
Those users had trouble syncing their files with the client, and trouble accessing their files in the browser. Myself, already having unlimited storage, could not get the root folder of my files to display in the browser and as administrator could not load the user administration page.
Now I have access to my root folder and these users can sync their files and access them normaly.