[Bug]: Segmentation Fault with new VFS on MacOS

[rakekniven]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Tried v3.13.0 from #6656 and after installation it does not start and gives Segmentation fault: 11 after start

Steps to reproduce

1. Install https://github.com/nextcloud-releases/desktop/releases/download/v3.13.0/Nextcloud-3.13.0-macOS-vfs.pkg
2. Start app
3. Seg fault is shown at console

Expected behavior

App should work like always

Which files are affected by this bug

nextcloud.app

Operating system

Mac OS

Which version of the operating system you are running.

13.6.6

Package

Appimage

Nextcloud Server version

29.0.0

Nextcloud Desktop Client version

3.13.0

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

No response

[camilasan]

I had multiple crashes with the VFS on mac OS 😅
on of them was solved with removing the nextcloud plist file in ~/Library/Preferences.
Quit the app, remove the plist file and start the app again.

In any case it would be interesting to know what you have in your crash logs.
You can check that in the Console app: on the left there is the option 'Crash Reports', you should have one called Nextcloud. Right click on the process name, click on 'Reveal in Finder'. You could attach the log here then.

[rakekniven]

Nextcloud-2024-05-05-192520.txt

Had to rename the file extension from ips to txt to make upload possible here.

[rakekniven]

In the mean time I had to install the normal version again. Tried the vfs on our family machine :-|

btw. I did multiple installation attempts yesterday and search the disk using the find any file utility to remove any relic incl. the plist file(s) -> no success.

[camilasan]

thanks for the info
@claucambra probably knows more

[claucambra]

@camilasan @mgallien is there a situation where AccountManager::accountAdded is reasonably sending out null accounts with the signal?

[Javihache]

Same problem here. I uninstalled Nextcloud, cause the sidebar icon is just a folder and thought I could solve that by reinstalling. Now Nextcloud 3.13 is not starting at all.

[Javihache]

I solved the issue removing all plists and other files in ~/Library, then installing 3.13 standard and finally installing 3.13 with VFS support. However the icon in the Finder Sidebar under Locations still shows a standard folder icon.

[claucambra]

I solved the issue removing all plists and other files in ~/Library, then installing 3.13 standard and finally installing 3.13 with VFS support. However the icon in the Finder Sidebar under Locations still shows a standard folder icon.

We cannot fix this, and it is the reason we have both a standard files client and a virtual files client on macOS; we have to pick between either providing the virtual files via File Provider APIs or being able to use the old Finder Sync API to decorate standard sync files and folders