fileproviderctl on Sonoma 14.4 - here we f#@%ng go again

[luckman212]

14.4 (23E5180j) seems to have gimped the fileproviderctl command again. This happened before where they completely broke the command on 13.6. Feels like there's ONE guy whose job it is to compile and keep this tool updated, and he's on vacation half of the year.

Critical commands that are now missing

- fileproviderctl evict
- fileproviderctl listproviders
- fileproviderctl stabilize
- fileproviderctl materialize
- fileproviderctl domain <...>

HN post: https://news.ycombinator.com/item?id=39251206

Well, Apple has spoken 😡

For reference, here are some related (possibly linked) bugreport numbers:

• FB13580772 (my report)
• FB13592689
• FB13674694
• FB13691058

 

[kitKAC]

Since 14.4 is beta, you've logged a Bug Report right?

 

[luckman212]

Yup sure did! FB13580772

 

[sashka]

Care to explain what these commands needed for? I don't see any of them in the `man fileproviderctl`, perhaps they were deprecated earlier? `listproviders` is shown in the help and seems like lists providers.

 

[luckman212]

They were not deprecated earlier - they are still present in macOS 14.3.

The commands are used to manipulate any software that uses the FileProvider API — well known examples are Google Drive, OneDrive, Dropbox, iCloud Drive, CloudMounter, Strongsync, and many others. The removed commands were useful for troubleshooting and fixing sync issues with these apps, espcially the evict and domain subcommands.

 

[luckman212]

Updated to 23E5191e - sad to report that there's been no change here.

 

[luckman212]

Just got this reply from the mothership...

We have determined that this issue is not to be fixed/changed.

Thank you for your feedback.

 

[Kathiresan A]

Thanks for giving this information!

 

[luckman212]

In case anyone's curious if 14.4.1 changes any of this, it doesn't.

 

[luckman212]

Anybody try 14.5 beta yet? Any changes to FileProvider or fileproviderctl?