Some additional data - Xcode debug windows shows CaptionEdit[1137:31772] Could not load the "gearshape.fill" image referenced from a nib in the bundle with identifier "com.AlekaConsulting.CaptionEdit" and "CaptionEdit[1137:31772] libMobileGestalt MobileGestalt.c:890: MGIsDeviceOneOfType is not supported on this platform." when images not shown

I think the answer is the that System icons/images are SFSymbols, which are only supported for iOS 13 or later. Doco recommends exporting as SVG and bundling with app to use in older versions using SFSymbols app

This problem often recurs, even with a new account and using the bash shell. Closing and re-opening Xcode seems to fix it.

After adding a subscription from a new Sandbox account (set in App Store Connect) the iPhone shows the email address of the new account as Apple ID: newemail, but clicking on only shows Cancel and Sign In options, not Manage.

Same problem with iOS 12.5.5 on iPhone 6

XCode 12.3 issue on Catalina appeared after deleting DerivedData Folder for project. Closing and re-opening XCode project, and cleaning build folder eventually worked.

Checking Hide Title Text in the panel attributes results in the expected display in Xcode 13.4 in design mode but when run, the application spaces the toolbar items so much that the right-hand ones disappear and are shown in a disabled menu

Rebuilt the toolbar in Xcode 13.4 but flexible space toolbar item does not have any width, so replaced with 3 regular spaces to give apperance as shown below. When run on Catalina the toolbar appears as in the first image.

Full crash log attached: Crash log (.ips file)

Thanks for all the effort you've put in to deal with this problem. Have you any idea why I can't reproduce it on my MacOS 12.4 machine? I may be writing to a log file outside the sandbox but I don't think it would cause the observed crash. I've tried running the app in a fresh account (using the distribute to development team archive option) on the dev Mac but it doesn't crash. A non-reproducible problem I'm having is that sometimes the app menu bar is unresponsive - sub-menus are only visible when the touchpad is pressed. The app then has to be stopped from Xcode or killed using Activity Monitor. Sometimes windows shown do not respond to the close button. Could these be connected with the crash which the app reviewer encountered?

I'm not able to further symbolicate the crash report from App Review as there is no Download Debug Symbols button shown in the Archive Organiser (shown in Xcode 13 with Window->Organiser) for the build which failed. I tried resubmitting and got the same result, only App Review has now moved to MacOS 12.5 and i have MacOS 12.4.

When I followed the procedure to symbolicate an external file by changing the .ips extension to .crash, adding an external device, viewing All Logs and dragging the .crash file from MacOS12.4 Finder to the LH column, a part of the log appear in the RH window but does not include any frame data. The last line is Crashed Thread: 0 Dispatch queue enabled. Right-clicking on the added file and selecting Re-Symbolicate Log results in nothing happening. If I click Done and open View All Logs again, the added file is not present. I presumed this was due to lack of debug symbols but from your comment this is not the case.

Do you think the reason I am unable to further symbolicate the .ips file is because I do not have the correct .dSym file? The Binary Images section of the .ips file is as shown below. Where is the required UUID? Can you tell me how to use dwarfdump to see if I have a .dSYM with the right UUID and how to use mdfind to see if it is visible to the symbolicator and what to do if it is not?

Hi Quinn I've had no success in following the symbolication instructions - mdfind does not find anything using the UUID in the frames containing the words Caption Pro. I tried creating an out-of-bounds array access to trigger an exception and the crash log indicated that this was the problem. On checking my log file, there seems to be no possibility of an out-of-bounds array access before the crash occurs, so the origin of SIGABRT is still unclear. I have added a lot more logging, including the created array item count and will resubmit in the hope of getting more detailed info on where the crash occurs. I have packaged the app for distribution to customers and asked a couple of Mac friends to see if they can run it on up-to-date machines. One of them has done so successfully, so the problem the App Reviewer has is still mysterious

The error found by App Review was indeed an out-of-bounds array access caused by my reading CFBundleVersion as the app version rather than CFBundleShortVersionString. CFBundleVersion is actually the build version. I had set this to the app version (3.1.25) and all users except the App store reviewers read this sucessfully and split the version number into components at the ., but the App Store review environment seems to replace whatever you put in the field with the number of times you've submitted to the App Store. so the value was a single integer, which could not be split at '.'. This is why I could never reproduce the crash. I never succeeded in symbolicating the crash logs from App review in Xcode and have raised a separate query about that. Thanks for your help - maybe it will help avoid more frustration for Mac developers