You can name a breakpoint, and reference it by name from another breakpoint’s work. You can re-order breakpoint actions by dragging and dropping them into a unique position. Like “Thread 1: breakpoint 1.1 (14), ” 14 means breakpoint 1.1 has been hit 14 times. Xcode 12 now displays the breakpoint hit count for a specific breakpoint location. This may be very helpful in large size storyboards. You can enable and disable this minimap with Editor > Canvas > Minimap. You can drag, double-click or command-click within the minimap to specialize in a selected area. Xcode 12 adds a replacement minimap for the Interface Builder canvas. You can also choose a single font and icon size for Xcode within Xcode Preferences. The project navigator now takes advantage of the system setting to resize “Sidebar Font & Icon Size,” almost like Finder. So, it’s more compact and takes up less screen space. Xcode 12 comes with a replacement code completion UI with only the knowledge you would like. With this updated model, you’ll re-arrange the document tabs to make a working set of files for your current task, and configure how content is shown within each tab. You’ll use these reports to optimize the disk-write performance of your apps. The organizer now also provides Disk Writes diagnostic reports. To look at the Scroll Hitch bar chart, click on the Scrolling section within the Metrics Organizer window. You’ll use these metrics to spot animation delays users encounter while scrolling in your application. The organizer now displays scroll-hitch metrics. Choose any app from any of your developer teams, then quickly navigate to examine crash logs, energy reports, and performance metrics, like battery consumption and launch time of your apps when employed by customers. Xcode 12 features an entirely new Organizer with an all-new design that groups all critical information about each of your apps together. With Xcode 12, SwiftUI views can now be shared with other developers, and appear as first-class controls within the Xcode library. So, now you’ll share life cycle code across all Apple platforms. SwiftUI has a complete new lifecycle management API for apps built with SwiftUI. The existing SwiftUI code continues to figure, with faster performance, better diagnostics, and access to further controls. SwiftUI (no SwiftUI 2.0) offers some new features with many performance improvements. Xcode 12 beta requires a Mac running macOS Catalina 10.15.4 or later.

Xcode 12 beta requires a Mac running macOS Catalina 10.15.4 or later.iOS nine and later, tvOS 9 and later, and watchOS 2 and later. The Xcode 12 beta release supports on-device debugging for iOS 9 and later, tvOS 9 and later, and watchOS 2 and later.

Xcode 12 release includes Swift 5.3 and SDKs for iOS 14, iPadOS 14, tvOS 14, watchOS 7, and macOS 11. And Xcode 12 builds macOS Universal apps by default to support new Macs with Apple silicon. Navigator fonts now match the system size or are often set to small, medium, or large. With Xcode-12, it is faster to open multiple files. Xcode is in the middle of all development on Apple’s platforms, and with Xcode 12, it’s a fresh update to match macOS Big Sur. This includes using the correct architecture, and also some options that can be found in the link that I had posted at the very top of this thread:Īlso, I am not using XCode 13 (still on 12, really dreading the upgrade, as I know this will break many things on my other projects), but I suspect that the configurations for a dynamic library will be very similar and should therefore work using the same guidelines (this has been my experience when migrating my projects from XCode 9 through 12, and even making the jump from 32- to 64-bit-the build settings are pretty much the same).Apple has announced Xcode version 12 at #WWDC20 they released the beta version on the same day. There may be a bit of config to do to make the XCode project build the external correctly. I don't know if this might make a difference, but can you try doing that and then loading the external in the debug scheme? I've always compiled the externals using the Build action in XCode (rather than running Makefile). My apologies for the months-long wait in replying.