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

I'm able to set the color of the back button in Objective C. UIBarButtonItem *backItem = [[UIBarButtonItem alloc]initWithTitle:@"" style:UIBarButtonItemStylePlain target:nil action:nil]; [backItem setTintColor:[UIColor logoRed]]; [self.navigationItem setBackBarButtonItem:backItem];

I accepted the answer since it was to my original question, of course now I still have an open question about presenting that hosting controller in a way so that it will show up as a glass sheet.

I have issues still with clear vs regular FB19374342.

Thanks. I've added the test project to my GitHub here. It's an objective c storyboard hosting sample code from this year's WWDC. (which btw would be nice if this sample were swift 6 compatible so the compiler doesn't complain.) I've managed to make the background this lovely gradient, thanks for the link. My mistake was in putting the background on the body, not inside the Navigation stack. Clearly I'm used to Storyboards. But what I really want is to have it show up as a glass sheet when I present it from my objective C app, but it's not doing that, either. I tried making the background clear, but it goes back to showing up as black. How do I make it show up as glass?

Could have sworn I added that I put the real FB in here a few days ago. Here's the right one, still happening on the latest betas. FB19209098 I deleted CoreServices, and now an app with iPad target runs the 18.5 simulator with latest Xcode 26 beta. However, my app with iPhone target now runs into this issue, runs fine in 18.5 release Xcode. FB19270537

Clearly I'm mixing up my FBs and going crosseyed. this one is actually this crash. FB19270537

Hi Ed, sorry about the wrong feedback. Ran into the problem again just now and submitted FB19209098. Happened in simulator and on device.

The selected segment also doesn't use our custom font and color, and instead just draws black.

Feedback: FB18304238. I have this problem as well specifically on a phone. I've subclassed UISegmentedController to be a deselectable segmented controller - I want the segment to turn off if the user taps the selected control. This works great on iOS 18-. On 26, I captured the touches ended, and rather than the proper segment for the geometry, (i.e touch at x310/320 should be index 2), it returns a sometimes random but mostly segment 0 as the selected index, rather than what the touches are reporting. My feedback has this log as well as a movie of the behavior.

I'm also seeing the issue. Duped because removing framework doesn't work. I think I need it for my extension to read NSURLs?? FB18733480 (My designer actually found - I usually only do beta stuff on beta, and was working in old Xcode for 18. Designer wondered how I didn't notice this bug. Which I did, as soon as I tried to run on 26 with 18 sim.)

Oh thanks for the reply. I meant that the content view is. being presented as a sheet itself. I tried the code above, and the child also has a black glass sheet. So, maybe pretend I don't present anything.

Are you able to rotate a layer an arbitrary amount (eg stopwatch hand to 90 degrees??

did you ever figure this out? I came back to a project to discover that dragging works, but white backgrounds are being added to my tableviewcells.