It doesn't work. What I'm asking is how to compile code containing new iOS 26 API using Xcode 16, which doesn't support these new APIs? This code does not compile, I get an error: Value of type 'UIBarButtonItem' has no member 'sharesBackground'. if #available(iOS 26.0, *) { addBtn.sharesBackground = false } I had to use this solution but it seems flimsy. #if compiler(>=6.2) if #available(iOS 26.0, *) { addBtn.sharesBackground = false } #endif

I discovered that the issue is not with going to the background, but with assigning the bar button item after the initial loading: "self.navigationItem.leftBarButtonItem = showFullScreenBarButtonItem()". I did create a test project, but I don’t know how to send you a link to an iCloud file, macOS Sequoia removed the option to simply copy a link, and now I need an email address in order to generate one 🙁. How should I send you the test project?

For anyone reading this, disregard the previous comment stating that you don't need "to set layer.contentScale recursively", you DO need to set it recursively, otherwise the text stays blurry.

Thank you for the boilerplate response. If you carefully read the thread, you'll see that I filed a FB already, also at the request of another boilerplate responder, only to be met with silence ever since. Check "Ed Ford,  DTS Engineer"'s response above; it includes four of my comments. "k.wridan" also filed one too - requesting FBs is just a way to deflect attention.

It's not only the static frameworks and self, but printing local variables has issues too, in frameworks and in the main app too. But sometimes it works and that's why I didn’t mention it. I don't know where the "*.swiftmodule" are located, that's Xcode's job.

I opened a thread here, maybe you can ask this Apple engineer more details, he didn't answer my further inquiries: https://developer.apple.com/forums/thread/771788?answerId=826459022#826459022.

Hi, have you had a chance to look at these bug reports?

Maybe you can leave a comment on the answer above, so Ed can see the Feedback ID https://developer.apple.com/forums/thread/771788?answerId=826459022#826459022.

Hi, I've filled a bug report: FB17038489.

Xcode 16.3 beta (16E5104o) exhibits the same issue.

I'll file a report in a few days, been busy with a release. What's strange is that it seems that it works for a few cases, of using 'po', but not for others. SwiftUI is used in one static lib, which exhibits the issue, but there is also another one which is not using SwiftUI at all, and still shows the issue. I did not check the Xcode 15.3, I'll do it right now.

Can we use SwiftUI constructively, or should we wait for a proper implementation of such basic things like the SwiftUI button ?

Thank you but that hardcodes the buttons width, and I'd like to avoid that.

It seems that I'm missing something, I applied that and it doesn't work, please see my response in the main thread, I can't attach pictures here.

Nope, the question is about the "distance between each screen" in AppStore, the gap between screenshots when they are displayed in AppStore.