If I understand correctly your problem, the simulators you can use depend on the minimum deployment you've defined for your app. Select the app in file navigator panel of Xcode select Targets select general Then set the minimum deployment to iOS 18 or lower if you want to use such simulators. Then, in the top bar of Xcode window, select the simulator as usual.

I've solved the issue with a workaround (until I understand what is causing the initial issue). I mimic clicking in windowA by sending a mouseDownEvent, and it works. self.window?.makeFirstResponder(self.window) self.theViewToClick.perform(#selector(NSResponder.self.mouseDown(with:)), with: newMouseDownEvent!)

I found something and potential solution. The NSPopover is created inside a windowController (window A). If I click in window A after opening the popover, all tooltips work correctly. What is the reason ? Could it be I did not set delegate for the popover ? I have tried to no avail I tried to make the window front and key No success either So there would be a workaround: simulate a click in window A What is the simplest way to achieve this click programmatically (if possible without showing mouse movement) ? Should I use mouseEvent(with:location:modifierFlags:timestamp:windowNumber:context:eventNumber:clickCount:pressure:) and then postEvent(_:atStart:)

I tested your 2 codes on Xcode 16.4 and Xcode 26.2. Same result for the first. With the second, different from yours: I still get emptyView.

Same problem if the tooltips are defined in Storyboard vs in code. I tested in another popover which only contains a TextField and 2 buttons: same issue.

Same here. -[AFPreferences _languageCodeWithFallback:] No language code saved, but Assistant is enabled - returning: fr-FR GenerativeModelsAvailability.Parameters: Initialized with invalid language code: fr-FR. Expected to receive two-letter ISO 639 code. e.g. 'zh' or 'en'. Falling back to: fr Mac is 15.7.3 Xcode is 16.4. Yes, I know, I'll have to update soon.

Have a look at this TN to check: TN3117: Resolving architecture build errors on Apple silicon | Apple Developer Documentation

In MacOS with AppKit, you get it directly in the storyboard, by activating the undo checkbox. Hope that helps.

…are not receiving what they paid for. When trying to reach out to Apple… For sure you have read your licence agreement: https://developer.apple.com/support/terms/apple-developer-program-license-agreement/ 2.10 Updates; No Support or Maintenance … Apple is not obligated to provide any maintenance, technical or other support for the Apple Software or Services. … So, even though that may be frustrating, they just meet their contractual obligation on that point.

Could you show a screenshot, in the case of this website ? Which MacOS version ?

That's not normal. You should contact support: https://developer.apple.com/contact/ Try to get a phone contact, much more efficient.

Welcome to the forum Warren85. It is hard to say with such limited information. You should read this to get tips on how to post on the forum: https://developer.apple.com/forums/thread/706527 This being said, please tell: Is it an iOS app (for iPhone / iPad) ? Is it SwiftUI ? Show the code of the app (ContentView if SwiftUI), we shall help you. Or at list the part where the initial content should show on simulator.

The error in case 1: implicitly unwrapping an Optional value. Second option works like a charm. And allows to add subviews in the box, easily.

Many thanks, I'll keep it. For the dark mode, it seems that Finder that Finder is doing in the same way:

Thanks for reply.   You definitely wouldn't want to change the highlight style in "viewFor". Maybe do that in viewDidLoad or something. What's the issue ?   There's more than one way to do this. One would be enough Anyway, I change my mind to stay consistent with system behaviour and will change the color of the text (to white) when selected, to make it more readable.