chromeOS 0byte files?

If you install the android seafile client on chromeos then seafile will appear as a service in the chromeOS file browser, however if you copy (or worse cut) a file using the chromeos file browser what actually happens is you end up with the file being truncated to 0bytes.

Opening the android App and adding the file via that works, but I’m guessing as the seafile server shows up as a location in the file browser and you seem to be able to access files hosted on the seafile server from the chromeos file browser it’s meant to intergrate.

Server Version: 7.1.8 (Pro) on an S3 backend.