Thanks again @RickMaddy I nicely added items to the File Menu using your example. As it turns out I was way overthinking this. I thought there would be a unified menubar in multitasking, not a per window one. This is much simpler and answered my, where is it in Vision, question. I don't really know how I missed this point in the intro video. The only other note I will point out for any other dinosaurs following along is that this line [super buildMenuWithBuilder:builder]; only works with supers that are UIResponder subclasses. So if you started your project in iOS 4.x your AppDelegate might still be an NSObject subclass, and you should upgrade to eliminate some build warnings.

FB20653877: Print Menu Doesn't show Preview with 'P' Key command (but does if you select print menu item) With P Key: With finger:

FB20653170: Autofill command still in Edit menu after using [builder removeMenuForIdentifier:UIMenuAutoFill]; in AppDelegate Nobody needs credit cards, contacts, or passwords in my app. They do want scan text, and I’d replace Autofill with Scan Text if I could. But I can’t so I want to get rid of something nobody will ever use. Here is my appDelegate method: (void)buildMenuWithBuilder:(id)builder { [super buildMenuWithBuilder:builder]; if (builder.system != UIMenuSystem.mainSystem) { return; } NSLog(@"Building menu for %@", builder.system);//it's building just checking [builder removeMenuForIdentifier:UIMenuAutoFill]; } I would expect if the option is there along with all the other menu identifiers, that one could remove the menu. But nope, there it is.

Adding FBs as I find them. FB20652137 Replace button wraps unfortunately. Going through all the built in functions menu by menu (Adding print was easy enough.) Added Find and Replace to my text views in storyboard, which automagically enabled the menu item and produced this view. I don't even have Text size that big in my iPad Air 13-inch sim. Also, in trying to see if you could replicate it with built in apps I notice that the input view I get is unlike the snazzy Pages built in keyboard. I wonder if there is a way I can adopt the Pages UX? I mean, I don’t mind the glass buttons but would like to choose the color for done (blue just doesn’t go with our look and feel). Or let me change the blue which really doesn't go with our Color scheme.

After asking DTS, in case anyone else is trying this, you want .containerBackground(.clear, for: .navigation) in your NavigationStack and override func viewDidLoad() { view.backgroundColor = .clear } In your hostingController subclass. presentationBackground(Color.clear) which was the initial answer, is not enough.

I duped this with a project, too. FB20448591

Same issue Xcode 26 (17A321), I've added FB20258577 with icon composer file and the inspector settings per layer. By blur do people mean Liquid Glass effects? Otherwise we have normal blend mode. The only way I was able to get a build uploaded today to fix my missing icon on the iPad target was to delete this file altogether. I have no idea why the iPhone target worked at all. Xcode Cloud was building for 2 hours today with no feedback. I finally archived myself and saw the validation errors with the red herring of it being in an asset catalog. So very tired but happy to have worked on betas again. I gave up on that when iOS 5 iCloud builds crashed every other launch and I had to revert three months of work. Not reverting Liquid Glass. It has issues, but it's very pretty when you give it a chance. It was inspiring to work with something beautiful amongst all the ugliness in the world these days.

For those following along at home it is possible. I put an overlay UIRepresentable on top of my swiftUI Cell. I use the object ID as accessibility ID. on tap, I send a notification triggering the segue, in prepare for segue I set up the zoom transition, which looks for the UIViewRepresentable to send to the zoom. Works even if I delete the detail and go to the next object in the list. Nice API.

I think this got fixed on the Xcode beta released today (6, but device version is beta 7). I say I think because it worked on my side, both 18.2 and 18.5. Very much appreciate everyone's time who addressed this.

When Apple compensates me hourly at your salary to devise sample projects for the bugs I find in your new stuff, maybe I'll take the time to do so. I have a day job, and my hobby is having a top 10 iOS app. I'm already working stupid hours to make your stuff look good (and have had the most fun since you made everything flat in iOS 7 and killed a bunch of joy so that's not actually a complaint). My report was mostly to help others with a workaround if they got themselves in that state. I mean, maybe I'm doing something weird here. I've isolated the bugs I care about in sample projects. It usually takes at least an hour to do a good job because I have a very complex view hierarchy. I'm not making a sample project for every bug for a trillion dollar company. That sounds like work, not something I should spend time away from my family for.

Amazing. Really thanks. So I make the superset in the app delegate, and if nothing in the active window handles it, the item is disabled. Very very much obliged.

I guess what I'm trying to wrap my head around is the guidance in the video from this year where it says, don't hide menu items, or change how the menu is built from under the user, just disable items, Build the menu once in appDidFinishLaunching, but then the menus get built by each scene type? I'm trying to go from a spit view ish one-window app, to multiple scenes, where there are different scenes and storyboards, so sure my window's root view controller can handle things, but each scene will have a different root controller, how do you build something that coalesces them all. I guess I could just experiment but the builder looks clunky enough that I'd be annoyed building something 5 times if I got the assumptions wrong. Thanks for the pointer, I've used that sample a lot already building context menus. (I'm also doing it all backwards in obj.c so I have to squint real hard at the swift.)

Um, just curious, I saw like 4 different versions of this post? What's the goal there?

Commenting this line in viewDidLoad or changing to softStyle brings it back. This seems like a good workaround. I was posting it in case someone else ran into it.

For anyone following along at home. I'm able to present SwiftUI controllers as glass in my objective-c storyboard app if I recursively keep setting subviews backgrounds to clear in my swift hosting view controller subclass. The offender with a background is "UIHostingView" I could turn it off by name but that's probably a bad idea. Maybe a 'hostsGlass' property on UIHostingController ? FB19403683