How can I create a simulator for an iPhone 6 (runninf iOS12.4) in Xcode 12.3? Entries in the Simulators list shown in Preferences->Components are all greyed out. The entries go up to iOS14.2. If I try to create a new Simulator by clicking + in Window->Devices and Simulators, Simulators tab, the only OS version available in the dropdown is iOS 14.3. If I try to download more Simulator runtimes I see the greyed out list shown in Preferences->Components.

I am developing an app to run on iOS 12.4 or newer using Xcode 12.3 on MacOS Catalina. On my screens I have a number of navigation bar buttons which have a system icon specified as well as text in Interface Builder. When running on an iOS 14.3 simulator, the bar button icons appear but on an iOS 12.4 simulator (and an iOS 12.4 device) the icons do not appear and only text is shown. The buttons still work OK on iOS12.4. How can I make system icons appear in Navigation bar button items in Xcode 12.4?

I'm trying to sign into a Sandbox account which is visible in App Store Connect from an iPhone 6 running iOS 12.5.5. After submitting Sandbox account or Apple ID credentials, a gear wheel appears but when it disappears the Sign In prompt reappears. If I enter invalid credentials, immediate feedback they they are invalid is shown.

An application toolbar in an XIB file created in XCode 12.3 on MacOS Catalina from an Objective-C project appears as below But in XCode 13.4 it appears as below (the rotate icon has been changed) When the application is run under Xcode 13.4 or on MacOS Monterey the application toolbar appears as below How can I make the toolbar appear as it does in Xcode 12.4 when running on Monterey or using Xcode 13.4?

No AppName.dSym file is generated in App Archive by Xcode 13 using the default settings ported from Xcode 12. Has a setting been lost which enables symbol creation?

I have an Objective-C app which ran OK on Catalina in Xcode 12.3 on a 2012 Macbook Pro. Since App Store will now only accept apps developed on Xcode 13, which does not run on Catalina (the newest OS that the 2012 Macbook will support) I purchased a 2019 Macbook running Monterey, in which I have Xcode 13.4.1 installed. When I run Xcode in Monterey it is much faster ( despite the slower clock rate of the 2019 machine) but a number of bugs have appeared. The major one is that a toolbar created in Interface Builder on Xcode 12.3 is not correctly formatted in an application built from Xcode 13.4.1, even though it appears OK in design mode. This bug was fixed by re-creating the toolbar in Xcode 13.4.1. When running in Xcode 13.4.1, Menu options sometimes do not appear at all and if they do appear, they only show when the touchpad is pressed and held down - they disappear if it stops being pressed. This applies to the Apple menu items as well. If the app is closed in Xcode, the Apple menu items appear normally. Other apps have their menus appearing and responding normally. If a toolbar item is clicked to show an NSPanel (via [ setIsVisible:true]; in this state, the NSPanel may not be shown and cannot be closed by clicking the red dot at the top LH corner. If the app is in the state where menus are not shown when the touchpad is clicked, adding a breakpoint in an action and resuming execution with ctrl-cmd-Y sometimes changes the app state so that menu items are shown as expected. Restarting Xcode does not change the app state, and nor does restarting the Mac or cleaning the build folder.

I have an Objective-C MacOS app originally developed in Catalina on a 2012 Macbook Pro and recently ported to a 2019 MacBook Pro running Monterey and using Xcode 13.4 in response the App Store no longer accepting apps developed in Xcode 12, which is the newest version supported by Catalina. The app is targeting MacOS 12.0 (Catalina). The app builds and runs OK on Monterey, but when run on Catalina it crashes and the crash log error reason (NSCFConstantString stringByAppendingString:]: nil argument) is incorrect, as diagnosed by a series of log statements. The statement on which it fails is calling setSelectionIndex on an ImagesController class, which uses the NSArrayController interface.

When running an Objective C app in Xcode 13.4 on Monterey on a 2019 MacBook Pro , app menu options sometimes only appear for as long the touchpad is pressed and the app is not responsive to menu selections. The Apple menu behaves similarly. The app can only be closed by stopping the run in Xcode. This behaviour is not reproducible - sometimes the menu appears normally.

have an Objective C app originally developed in Xcode 12.3 on Catalina and ported to Xcode 13.4 on Monterey. The minimum OS version is set to 10.12 (Catalina). In the app is a class ImageController defined as below, with a number of functions ImageController.h #import <Cocoa/Cocoa.h> @class AppDelegate; … @interface ImagesController : NSArrayController {     … - (void)addFileAtIndex:(NSString *)filePath index:(NSUInteger)index; } ImageController.m #import "ImagesController.h" … #import "AppDelegate.h" … @implementation ImagesController - (void)addFileAtIndex:(NSString*)filePath index:(NSUInteger) index{ ... NSMutableArray *filesToAdd = [NSMutableArray array]; [filesToAdd addObject:[CSSImageInfo containerWithPath:filePath]];       NSMutableIndexSet *indexSet = [NSMutableIndexSet indexSetWithIndex:index];        self insertObjects:filesToAdd atArrangedObjectIndexes:indexSet];        NSInteger selectedIndex = [self selectionIndex]; …     } When the function addFileAtIndex is called (with [imagesController addFileAtIndex:filename index:selectedIndex]; the app running on Monterey it executes normally. When is is called from the app running on Catalina it is never entered. What do I have to do to make the function accessible on Catalina?

Can MacOS apps be downloaded from outside the App Store as well as from it? I'd like to make it available directly from my web site as well as within the App Store.

I would like to record application log data in a file which iOS users can locate using the Files app and email to me in case of problems. Can I do this using the os_log functionality? The file path is defined as below: let paths = NSSearchPathForDirectoriesInDomains(.documentDirectory, .userDomainMask, true)         let documentsDirectory = paths[0]         let fileName = "\(Date()) CaptionEdit Logfile.txt"         let logFilePath = (documentsDirectory as NSString).appendingPathComponent(fileName)

I have a Swift 5.0 iOS app in Xcode 13 targeting iOS 14 where I try to access the Google Photoscan app programmatically using the following code running on an iPhone 8 with iOS 16 let photoScanURLString1 = "https://apps.apple.com/au/app/photoscan-by-google-photos/id116552994"             UIApplication.shared.open(NSURL(string:photoScanURLString1)! as URL) This takes me to the App Store and shows the message "This app is currently not available in your region or country", which is en-AU, but does not go to the App page and let me download. The same behaviour is observed if I enter the URL photoScanURLString1 into Safari on the iPhone. However, if I click the URL in a mail message I can download the app, and if I search for Google Photoscan in the App Store app I can download it OK. How can I download the app from the App Store programmatically without changing my region in the iPhone settings?

The Main storyboard in an Xcode 14.01 Swift project workspace shows all panels as blank, Opening the Main.storyboard file (in Base.lproj folder) with Xcode shows it as expected but it appears blank when loaded into the project. Removing and adding the file does not show its content in Xcode.

I have been using an "Elements SE" 1 Tb USB hard drive for Time Machine backup on a 2012 MacBook Pro running Catalina, where it worked OK. When I plug the drive into a 2019 MacBook Pro running Monterey, Time Machine cannot write to it as it appears as read-only. Whe I try and inspect the disk using Disk Utility it appears as unmounted, and greyed out, and the Mount button is greyed out. First Aid on the disk fails. What do I have to do to make it useable by Time Machine on the 2019 MacBook Pro?

I have an Objective-C app running on MacOS using XCode 14.1, in which there are 3 levels of form. The Level 2 form is opened from an action with a makeKeyAndFront action from a button. The Level 3 form is a regular panel opened from the level 2 form in a similar way. The level 3 form can be closed normally if no action changes the level 2 form. However, if an image is loaded into an NSImageView control on the level 2 form, the level 3 form can be displayed but cannot be closed by clicking on the red x button which normally performs this function. The level 3 form can be minimised. What do I have to do to allow the level 3 form to be closed in this situation?