Others have asked, no reply so far: https://developer.apple.com/forums/thread/649962

I cannot find anything wrong in this small code. And the fact it prints nil shows the action is correctly connected. A possible reason would be the state of button is not normal. I tried with the exact same button definition and it works. Could you try : to be sure of what is called, replace print by print(#function, sender.title(for: .normal)) print("Sate", sender.state) add a print to test the titleLabel           print(sender.titleLabel) and test the button itself: print(sender) print(button) What do you get ?

Did you copy the code exactly ?

That confirms that the reason is that the button is not in normal state and that its title for normal state is not defined. Which is surprising. Which version of Xcode do you use ? Could you do another test by printing in the IBAction: print("normal", sender.title(for: .normal)) print("highlighted", sender.title(for: .highlighted)) print("disabled", sender.title(for: .disabled)) print("selected", sender.title(for: .selected)) print("focused", sender.title(for: .focused)) I tested with the same button definition (Style plain). It works and the sender button content is the same as yours: <UIButton: 0x7fa72e70b990; frame = (99 664; 214 34.3333); opaque = NO; autoresize = RM+BM; layer = <CALayer: 0x600003c315e0>> configuration=<UIButtonConfiguration: 0x600000073100> baseStyle=plain macStyle=automatic buttonSize=medium cornerStyle=dynamic title=<0x600003c31760>:'Aaron' contentInsets=default imagePlacement=leading imagePadding=0 titlePadding=1 titleAlignment=automatic automaticallyUpdateForSelection background=<UIBackgroundConfiguration: 0x60000096b300; Base Style = Custom; cornerRadius = 5.95; backgroundColor = UIExtendedGrayColorSpace 0 0> Could you test with a default style for button, instead of plain ?

This has disappeared in Xcode 13, On the left Xcode 12, on the right Xcode 13: Xcode 13 Release notes explain: The project navigator hides the Products group when it’s in the default location. The Product > Show Build Folder in Finder menu item replaces the most common use. (71561549) Don't worry, usually you have no need to access it.

If you mark your "answer" as correct, no one will reply.

Could you show the code: of the originating VC (VC1) of the destination VC (VC2 with the search bar) Also show how you defined the segue from VC1 to VC2

Could you explain the context ? access example scripts for script editor Do you mean scripts in Xcode ? Or elsewhere ? I know how to access the folder Which folder ? using a shortcut key If you mean a custom key for Xcode, you define them in Preferences -> Key bindings tab.

Haven't you other crash information ? This describes system config, but nothing on the crash itself. Did you reproduce the crash in simulator ?

Did you try:  switch annotation.title {         case "0": But if you know the name of annotations (One, Two…), no need to add a number before. But if the title is dynamic, that will be very useful.

You certainly have good reason for it, but that's a pretty complex layout. Setting constraints for CollectionView or for StackView is always tricky. I would suspect that the problem comes from embedding UICV2 in a stackView. Could you test removing the Stack view ?

At what stage exactly of the submission process ? Could you? : tell exact Xcode version show a copy of the page where the message occurs Note : I am submitting apps with Xcode 13.0, MacOS 12.6, without problem.

You are not the only to have this problem: https://developer.apple.com/forums/thread/693033?answerId=692478022 Could you? : tell exact Xcode version copy the page where the problem occurs Note : I am submitting apps with Xcode 13.0, MacOS 12.6, without problem.

The reverse seems to occur: return true when should return false. https://developer.apple.com/forums/thread/693036 You should file a bug as the problem seems to persist.

I read in this other thread: https://developer.apple.com/forums/thread/130321 Strangely enough, isCaptured indeed returns false while mirroring a FairPlay protected stream. Looks like a bug.  Just as if the value was reversed (false for tue, true for false). You should file a bug report. In the meantime, you could use !UIScreen.isCaptured. Not very clean, but may be a work around.