{"id":37888,"date":"2022-12-14T14:44:05","date_gmt":"2022-12-14T19:44:05","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=37888"},"modified":"2022-12-14T14:51:30","modified_gmt":"2022-12-14T19:51:30","slug":"xcode-14-2","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/12\/14\/xcode-14-2\/","title":{"rendered":"Xcode 14.2"},"content":{"rendered":"

Apple<\/a> (download<\/a>, command-line tools<\/a>, additional tools<\/a>):<\/p>\n

\n

Xcode 14.2 includes Swift 5.7 and SDKs for iOS 16.2, iPadOS 16.2, tvOS 16.1, watchOS 9.1, and macOS Ventura 13.1. The Xcode 14.2 release supports on-device debugging in iOS 11 and later, tvOS 11 and later, and watchOS 4 and later. Xcode 14.2 requires a Mac running macOS Monterey 12.5 or later.<\/p>\n<\/blockquote>\n\n

I don’t see anything about it in the release notes, but fingers crossed this fixes the bug I’ve been seeing where changes to some source files don’t get compiled into the final binary unless I do a clean build. I keep seeing “impossible” behavior only to realize that it’s because old code is running.<\/p>\n\n

Daniel Kennett<\/a>:<\/p>\n

\n

I had a quick spelunk and there’s a user defaults key that looks promising for turning off these adverts Apple has put into Xcode 🤞<\/p>\n

defaults write com.apple.dt.Xcode XcodeCloudUpsellPromptEnabled -bool false<\/pre>\n<\/blockquote>\n\n
Previously:<\/p>\n