Aliases broken in macOS File Provider

[Levin040]

Hello everyone,

I recently switched to Virtual Files Client for testing purposes to see the features and identify any issues.
I liked the way it worked.
However, I have a workflow where I keep creating aliases for folders that I then link on the desktop. And that doesn't work. My question now is whether I need to customize something or if I should wait for the next version.

Kind regards Levin

[bilogic]

Yea, aliases do not work as expected, bug?

[i2h3]

I can confirm that the creation of aliases is not handled correctly by our code. As a workaround until this is fixed, it might be an option to create symbolic links manually in the Terminal like this (I tested this in ~/Desktop and it worked):

$ ln -s /Users/iva/Library/CloudStorage/<file-provider-domain>/Nextcloud\ intro.mp4

[i2h3]

I just noticed in the code which makes sense: Symbolic links themselves cannot be created within the file provider domain itself because Nextcloud does not support synchronizing them, as far as I know. But the aliases are something different, actual files, similar to what I know from Windows in the past.

I need to check how the work exactly and whether we can do anything about this at all, even if just preventing their creation entirely. It is a file (and its content) created by macOS and it is synchronized successfully.

[bilogic]

I think the use case is to symlink a nextcloud folder to say the desktop using the UI, and not so much of a MacOS alias, which I'm not sure what it is exactly on the filesystem