You get the new glass look automatically. Just create normal UIBarButtonItem instances with appropriate images and set them to the view controller's toolbarItems. You automatically get the look in the second picture. You just might need to correctly use fixedSpace or flexibleSpace to get the proper spacing. See Build a UIKit app with the new design. Jump to the "Navigation and toolbars" section. If you still need help, post your relevant code to get better help.

The Pop-up button page in the HIG has a link to SwiftUI MenuPickerStyle along with a link to NSPopUpButton for AppKit. I'm actually not familiar with AppKit or SwiftUI (just UIKit) but hopefully that points you in the right direction.

If you don't want to backup the simulators, then setup Time Machine to exclude ~/Library/Developer/CoreSimulator If you don't want to backup the derived data used during builds, then exclude ~/Library/Developer/Xcode/DerivedData

I forgot to mention that the Feedback Assistant now (as of a day or two ago) has much saner options for versions. Thanks. P.S. I just saw your comment confirming this as well.

Unfortunately iOS 26 no longer honors any tintColor set at the UIWindow, UINavigationBar, or UIToolbar level for any glass components. So this includes any UIBarButtomItems including standard back bar items. As you've seen, you can only tint individual bar button items. Everyone affected by this should file a bug report using Feedback Assistant so Apple knows that this needs to be fixed.

UISlider now has a trackConfiguration property of type UISlider.TrackConfiguration which in turn has a neutralValue property. I can't speak to a SwiftUI Slider.

Lots of bugs with UISlider.TrackConfiguration. neutralValue only works if the slider's min value is 0.0 and the max value is 1.0 and the slider's value is between 0 and 1. And of course neutralValue is also in the range 0...1. allowsTickValuesOnly is not honored if ticks are set. Even when set to false it acts as if it is true. enabledRange only respects the upper range, not the lower range. Time to file a bug report. P.S. You can work around the neutralValue issue by converting the slider's value of 0...1 with let desiredValue = slider.value * 20 - 10. That will give you a result in the range -10...10.

It's not missing. It moved. It's now in the bottom-left corner of the Interface Builder area of the screen. It's just to the left of the filter search bar, just above the "Deactivate Breakpoints" button.

hidesBottomBarWhenPushed is working fine for me with iOS 26 for showing/hiding the toolbar. You need to provide details on your setup.

Your screenshots are showing a tab bar. hidesBottomBarWhenPushed is for hiding a toolbar. From the documentation for hidesBottomBarWhenPushed: A view controller added as a child of a navigation controller can display an optional toolbar at the bottom of the screen. The value of this property on the topmost view controller determines whether the toolbar is visible. If the value of this property is true, the toolbar is hidden. If the value of this property is false, the bar is visible.

A quick search points me to the ProcessInfo class and its beginActivity(options:reason:) and endActivity(_:) methods. The options you can pass to beginActivity include preventing sleep. See the documentation for ProcessInfo for more details and examples. And yes, UIApplication is specific to iOS.

I filed FB18101140 last week. Hopefully the issues will be resolved soon. Looking forward to the next beta release.

I have a Mac Catalyst app that uses CoreLocation and MapKit (along with many others) and it builds and runs fine on macOS 15.5 using Xcode 26 beta 2. I do not have the same issue you are reporting. Though my minimum deployment target is iOS 15/macOS 12. Not sure if that makes a difference.

What is the full command line you are using to generate that output? When I use otool -L MyApp.app/Contents/MacOS/MyApp I only get 2 lines of output and my app links dozens of libraries.

Comparing your list to mine, your app is using the following libraries that mine is not using. Maybe this will help you figure out which is the issue: SafariServices.framework WatchConnectivity.framework WidgetKit.framework libswiftMapKit.dylib _LocationEssentials.framework AppIntents.framework Combine.framework CoreTransferable.framework DeveloperToolsSupport.framework Intents.framework libswift_Concurrency.dylib libswiftAccelerate.dylib libswiftAVFoundation.dylib libswiftCoreAudio.dylib libswiftCoreMedia.dylib libswiftCoreMIDI.dylib libswiftIntents.dylib libswiftObservation.dylib My app has quite a few that yours doesn't but those would be irrelevant to your issue. My app is also more Objective-C based so I'm using fewer Swift libraries. libswiftMapKit would be my first guess. I use MapKit.framework but not that Swift-specific MapKit library.