As I search around the internet this seems to be a common problem for the last 10 or 12 years. Someone must have a simple answer without hacks or work arounds. I ended up editing the “ FILEBASENAME.playground ” template files to import SwifyUI instead of Cocoa. That works but seems redundant for some reason.
lledsmar
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
No good answers yet. I'm sure that somewhere along the line I have done something wrong but what that might be has me at a loss. I am still using a work around by having edited the template so that a new macos playground file imports SwiftUI and Cocoa upon opening ( only saves a couple of seconds ) but it still doesn't seem right to me even though it all builds correctly.
A new project for macos imports only SwiftUI and so far seems to work ok
thank you Claude31