I just installed the release candidate last night, and now most apps can't capture my webcam's full resolution. It's a Logitech C615, and it supports 1080P 30fps, but only over MJPEG. Now apps are either capturing incredibly choppy video, or capturing at the low resolutions the camera supports over RGB.

Is it possible to control how Xcode Cloud versions the apps it builds? I would like to declare it to use the same template that my build system uses to generate its own Info.plist at build time: CFBundleVersion: [number of commits since a specific Git tag where I forked the project] CFBundleShortVersionString: [the same thing] And I want it to preserve the generated tags that I add to the Info.plist for informational purposes: GitHash: [the full commit hash that was built] GitVersion: [number of commits as used above]-g[minimum characters of hash to be unique, currently up to 8 now] BuildTime: [current date/time when Info.plist was generated near the end of build time] Is there any way I can automate at least the CFBundleVersion and preserving the rest of the custom tags with Xcode Cloud? Xcode Cloud unfortunately seems to completely override my version field, and sets it to the first 5 characters of the Git commit hash, which is incompatible with App Store version policy of only being numbers or dots.

I have no idea how to solve this. I am not using many local variables, yet I am hitting the 512 KiB stack size limit for secondary threads. My app has already been close to hitting this, now it's definitely hitting it. How the heck do I trace this down? Instruments has nothing about stack memory usage.

I get this errorif I either attempt to install to an empty APFS partition, or if I convert a working HFS+ partition and attempt to reinstall onto it to make it bootable.