The Packaging collection of build settings has the build settings for automatically generating an Info.plist file. To access the build settings, Select your project from the left side of the project window to open the project editor. Select the app target from the left side of the project editor. Click the Build Settings button at the top of the project editor. Typing Info.plist in the search field in the build settings list will show the build settings that deal with the Info.plist file.

Objective-C takes the C language and adds support for object-oriented programming. The function example you showed for iOS is an example of an Objective-C method. A method is a function that is part of a class. Objective-C methods put the return type in parentheses, (void). Objective-C has two types of methods: instance and class. An instance method starts with - while a class method starts with +. You showed an example of an instance method. The function example you showed for Mac is an example of a C function. Objective-C supports C functions. C functions do not put the return type in parentheses. C does not have classes so it does not have methods. Apple provides the following guide to Objective-C: https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/Introduction/Introduction.html The following book teaches Objective-C for people who already know Swift: https://www.hackingwithswift.com/store/objective-c-for-swift-developers

This question got a response in Apple's Q & A Slack https://appledeveloper.slack.com/archives/C043025CS59/p1670878510681929 The suggestion was to limit the content types using the .fileExporter modifier. I haven't written any code to open a Save panel when saving the document. I have the default SwiftUI behavior. How would I use .fileExporter when someone chooses File > Save?

This is a limitation in SwiftUI. I followed the following feedback: FB11876082

It's been 10+ years since I used SDL so I can't provide an answer to your specific question, but I can provide some help for you to accomplish your goal. File loading code from SDL articles and tutorials aren't going to work well on Mac because Mac apps have a different structure. Mac apps are app bundles that look like a single file in the Finder but have folders and files inside them. You can examine the contents of app bundles in the Finder by selecting a file, right-clicking, and choosing Show Package Contents. In a Mac game the sound and image files are in the app bundle. Windows and Linux do not have app bundles. If you use code to load a sound file, such as the following, in a Mac game: Mix_Chunk* sound = Mix_LoadWAV("sounds/rm1.wav"); The game won't be able to find and load the file. The big thing to get file loading to work properly with SDL on Mac is to create an Xcode project that creates an app bundle, not a command-line tool project. You may be able to find SDL Xcode project templates on GitHub or at the SDL site that take care of things for you. But you can also create an App project that uses Objective-C as the language and storyboards for the user interface. Delete the .m, .h, and storyboard files from the project. Add SDL and your C++ code. The following tutorial is old so the screenshots are going to look very different, but it shows how to set up SDL2 with Xcode: https://www.meandmark.com/blog/2012/01/using-sdl-with-xcode-4/ The following Reddit thread has a link to a newer article on using SDL with Xcode: https://www.reddit.com/r/Xcode/comments/zi9oku/how_do_i_set_up_sdl_with_xcode/

Open the project editor by selecting the project file from the left side of the project window. Select the app target from the target list on the left side of the project editor. Click the General button at the top of the project editor. Go to the Minimum Deployments section to set the deployment target.

You can set the device orientations your app supports from Xcode's project editor. Open the project editor by selecting the project file from the left side of the project window. Select the app target from the target list on the left side of the project editor. Click the General button at the top of the project editor. Go to the Deployment Info section Select the checkboxes for the iPad orientations you want to support.

The error message says there was an error compiling your code. The actual errors should appear in the issue navigator (shown in your screenshot) or the report navigator (Press Cmd-9 to open). Your screenshot isn't showing any additional errors. If you choose Product > Clean Build Folder in Xcode and build the project, does the error go away? If not, do additional errors appear in the issue navigator? Did you make any changes in your code recently before building the project? For anyone to provide additional help, you need to provide more information on what you were doing before you got the error.

The problem is more likely to be in the storyboard than in the code you provided. What is the class name of the view controller in the storyboard's identity inspector? Choose View > Inspectors > Identity in Xcode to show the identity inspector. The class name in the storyboard needs to be the name of your view controller's class, ViewController in your code example. What is most likely happening is the view controller's class is UIViewController in the storyboard. UIViewController doesn't have a buttonPressed selector, ViewController does. If you change the name of the class to ViewController, the error should go away. Is the IBAction connected? There should be a filled-in circle next to the line of code in Xcode's editor. If the error persists, you will have to provide more information on how you set up your storyboard for anyone to help you.

You need to provide more information for anyone to help you. What happens when you open a project? Be specific and detailed. Are you able to create a new project?

You would not be able to submit apps to the App Store with macOS 10.13. Currently you need to use Xcode 13 to submit apps to the App Store. Xcode 13 requires macOS 11. Pretty soon this requirement will be bumped up to Xcode 14, which requires macOS 12. You listed macOS as a tag. With macOS 10.13 you could create Mac apps for people to download and install on your own site, bypassing the App Store.

The most likely cause of your problem is that you did not explicitly specify the interface when creating the project. Xcode defaults to using SwiftUI for new projects. SwiftUI does not have view controllers. You must explicitly choose Storyboard from the Interface menu when creating the project to get a view controller file. The following article has more detailed information: https://www.swiftdevjournal.com/xcode-11-missing-view-controllers/

Does this mean that old apps making new app store updates would also have to build with Xcode 14.1 and the iOS 16.1 SDK after April 2023? I'm 99 percent sure the answer is Yes.

Apple doesn't have your source code to download. You should have the code on your Mac if you developed the app. If someone developed the app for you, they have the source code. Get the code from them.

I've tried running instrumentation to figure out what is going on here, Do you mean you profiled the app with Instruments? If so, what templates did you use? I recommend profiling your app with Instruments. Choose Product > Profile in Xcode to profile with Instruments. The App Launch, SwiftUI, and Time Profiler Instruments templates will help you find what's taking so long. The App Launch should help if the slowness you're experiencing occurs when launching your app. You may also find the following article helpful: https://www.swiftdevjournal.com/finding-the-slow-spots-in-your-code-with-the-time-profiler-instrument/