I have Safari Technology Preview Release 116 (Safari 14.1, WebKit 15611.1.5.3). When I start STP, regular Safari (Version 14.0.1 (15610.2.11.51.10, 15610) starts up right behind it. Always. If I start 'regular' Safari only, STP does not start. Anyone else having this issue?

So, I'm installing the Big Sur betas. With every beta, some Apple process uninstalls (or deletes) CommandLineTools (CLT). Yesterday, my system looked like this: Xcode: 12.4.0.0.1.1610135815 CommandLineTools: 12.4.0.0.1.1610135815 Today - prior to installing the latest beta, 11.3 beta 8, I checked for the existence of CLT. CLT was gone. Xcode: 12.4.0.0.1.1610135815 CommandLineTools: not installed 1) Why is this happening? 2) Is there a way to prevent this? After the beta is installed, I simply reinstall the same CLT I had previously. .

Running 11.3 beta 8. System hangs on shutdown (usually takes 4.5/5 minutes) This has been happening for a while (at least since Big Sur 11.1). Booted to recovery and ran first aid on all partitions. Only received errors on Macintosh HD - Data: Running First Aid on “Macintosh HD - Data” (disk2s2) Repairing file system. Volume was successfully unmounted. Performing fsck_apfs -y -x /dev/rdisk2s2 Checking the container superblock. Checking the EFI jumpstart record. Checking the space manager. Checking the space manager free queue trees. warning: Unable to read apfs keylocker ranges: No such file or directory Checking the object map. Checking volume. Checking the APFS volume superblock. Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking the extent ref tree. Checking the fsroot tree. warning: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (18406479 + 13) warning: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (95055863 + 216) warning: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (95058867 + 883) Verifying allocated space. Performing deferred repairs. The volume /dev/rdisk2s2 appears to be OK. File system check exit code is 0. Restoring the original state found as mounted. Operation successful. 1) "Unable to read apfs keylocker ranges". Is this a problem? 2) Are the cross check mismatch errors something that can be 'fixed' with first aid? I've booted to recovery mode, ran first aid 3 times, errors persist. I have Apple Care (and backups). Wanting to know if this indicates I should replace my internal HD? Thank you.

Watching this - https://developer.apple.com/videos/play/wwdc2019/714 Anyone succesfully build this - https://developer.apple.com/documentation/networkextension/filtering_network_traffic with the tools/versions in the title? I get a bunch of Redefinition of module 'AppleTextureEncoder' in module.modulemap. In addition to AppleTextureEncoder I see: 'Compression' 'Darwin' 'asl' 'dnssd' 'launch' 'os' 'os_object' 'os_workgroup' (and on and on). Finally, build fails with: "No such module 'NetworkExtension'.

I'm trying to start an emacs 27.2 daemon on Big Sur with the following plist: <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>gnu.emacs.daemon</string> <key>ProgramArguments</key> <array> <string>/Users/me/src/gnu-emacs/27/emacs/nextstep/Emacs.app/Contents/MacOS/Emacs</string> <string>--bg-daemon</string> </array> <key>RunAtLoad</key> <true/> <key>ServiceDescription</key> <string>Gnu Emacs Daemon</string> </dict> </plist> The process starts fine and I'm able to access the process. However, the path for the application launched is not the past from .zshrc. If I start the application from terminal or Finder, the app loads -AND- the path is as expected. How do I add an environment variable (such as PATH) to a LaunchAgent?

Prior to Ventura betas, I was able to determine the version of Xcode and CLT with the following script: # https://apple.stackexchange.com/questions/180957/determine-xcode-command-line-tools-version # This worked on Big Sur (ARM) 11.1 beta # Xcode if pkgutil --pkgs=com.apple.pkg.Xcode >/dev/null; then echo Xcode: $(pkgutil --pkg-info=com.apple.pkg.Xcode | awk '/version:/ {print $2}') else echo Xcode: not installed fi # Command Line Tools for Xcode if pkgutil --pkgs=com.apple.pkg.CLTools_Executables >/dev/null; then echo CommandLineTools: $(pkgutil --pkg-info=com.apple.pkg.CLTools_Executables | awk '/version:/ {print $2}') else echo CommandLineTools: not installed fi Working with the Ventura 13.0 beta (22A5321d), I have Xcode 14.0 beta 5 (14A5294e) installed as well as CLT 14.0.0.0.1.1658620134. The output of the above script tells me that Xcode is not installed. Xcode was installed from the developer downloads (not the App Store). Xcode: not installed CommandLineTools: 14.0.0.0.1.1658620134 Has something changed with the pkgutil utility or the way Xcode reports itself to pkgutil?

Looking for a dynamic table that displays the latest supported CLI versions with the version of macOS. Specifically, is CLI 15.3 supported on Ventura 13.7.8? More generally, what is the lastest version of CLI supported on macOS <version_goes_here>