Nobody from Apple will comment on this? It's very aggravating.

I am still curious why there is no explanation of why these crucial commands were removed?

Just chiming in here as I am the author of FB13580772. I sincerely hope someone at Apple will take this into consideration and bring back the removed functions in fileproviderctl: fileproviderctl evict fileproviderctl listproviders fileproviderctl stabilize fileproviderctl materialize fileproviderctl domain <...> I am really suffering to troubleshoot FileProvider issues on my machines since making the mistake of updating to 14.4.x

Did anyone figure out how to solve this? I am also getting this Cannot find "MyApp.xcodeproj/../YES" error from agvtool (Xcode 15): $ xcrun agvtool next-version -all Setting version of project MyApp to: 3. Also setting CFBundleVersion key (assuming it exists) Updating CFBundleVersion in Info.plist(s)... Cannot find "MyApp.xcodeproj/../YES"

Just adding that I copied the /usr/bin/fileproviderctl binary from a working 13.5.2 system, and tried running it. It crashes in the same way. So whatever bug exists here, doesn't appear to be with fileproviderctl itself, but rather with AMFI or some other security clusterf*ck. I guess we're done with Ventura anyway, bring on Sonoma this Tuesday with whatever new bugs they've cooked up for us...

console screenshot

Same issue here. 13.6, MacBook Air M2 2022

Same problem here! Ventura 13.0.1 + Xcode 14.1 I don't have a paid Apple Developer account, I just want to generate a fresh codesigning cert for local testing. Help!

Sounds like you might be using the 3rd party "flavor" of tccutil from https://github.com/jacobsalmela/tccutil try specifically running: /usr/bin/tccutil