Thank you for your confirmation and suggestion. Apple has not responded yet. I'm pretty new to Catalyst and I was hoping there would be a simple fix. I've looked high and low on a way to implement your suggestion but it still eludes me. I've tried moving the delegation around too. It also looks The code for this tutorial is somewhat complex so if you can provide any actual coding to make it work I would be most appreciative!

After some more looking around and patience I finally was able to get a working toolbar. From what I've read, Catalyst has a lot of shortcomings and this is one of them. It takes a lot more work to get things working the way they should.

I've submitted several FB requests about isssues with the tutorial, but so far none have been answered :(

Unfortunately I don't think you can view anyone else's feedback/bug reports except your own. Apple used to make filed bug reports available to all developers but stopped doing that for some reason. Seems kind of unproductive to me as no one can tell whether issues are being addressed or if you're about to file a duplicate report. I've had the same issue as OP (iOS16 only) but I haven't bothered to file a feedback since none of my other feedbacks have been answered.

@JbXyz: It would take too much space and time to provide program listings, but the basics are this: In Info.plist you enable multiple windows via Enable Multiple Windows, provde a Scene Configuration in Application Scene Manifest Application/Session Role describing the Configuration Name and Delegate Class Name of the scene/window you want to use. You then configure and instantiate the scene at the appropriate time (such as a button press) in your program.

I think this warning is harmless, but not entirely sure.

That's good information. I really just have (mostly) ignored the warning because I believe it to be log noise and use the #if targetEnvironment(macCatalyst) if a problem actualy does occur. It appreciate your input and will be on the lookout for the issues you found.