Looks like this feature was added to App Store Connect as of today, December 3 2020.

The code as shown cannot possibly be triggering the action for button #11. You must be running some different code. Anyway, I would check the view debugger to see if there’s some other view getting the touches in front of the button, and make sure your button’s frame is what you expect. The default for clipsToBounds is false, so if the frame is messed up a view can have all of its contents visible outside its bounds but it will not receive touches.

Not sure, probably a relatively harmless iOS bug. But you should be aware that a UIAlertController’s view hierarchy is considered private API. If you need a customized alert you need to roll your own view controller. Modifying UIAlertView directly has burned many developers in the past as the underlying implementation is subject to change at any time. I’m sure the same will happen with UIAlertController eventually. From the documentation: “Important - The UIAlertController class is intended to be used as-is and does not support subclassing. The view hierarchy for this class is private and must not be modified.”

Assuming your constraints / resizing mask can give UIKit enough info to correctly resize the cell, calling beginUpdates / endUpdates on the table view should cause it to resize any visible cells with animation. You shouldn’t actually need that animation block you’re currently using, I think.

Garbage in, garbage out. I believe that duplicate items/sections *is* the point. Frankly I’m surprised the API calls don’t throw an exception when presented with such invalid input. Anyway, maybe it’s due to how your identifiers are hashed? You’re using numbers in one case and strings in the other. If you use the same type of identifier, does that affect anything?

Well, there’s probably something going on in the code you’re not showing. Perhaps you have a gesture recognizer or target/action set up somewhere that’s being attached to the cell or a subview but never removed when the cell is reused. Perhaps your toggle method is being called twice, causing it to appear as if nothing has changed. A simpler, complete example (small enough to post all the code) would be easier to diagnose.

Good question, but the docs do state that identifiers must be unique. You’re attempting to append some items/sections that are not unique so I would expect the behaviour to be undefined. Perhaps you should be using the move or delete APIs to handle your duplicate items?

You won’t get to the rejection stage. The App Store won’t accept binaries built with Xcode 12 until the golden master has been blessed by Apple. That’s usually not until a week or two before the final public release of the OS. You can only submit production builds using Xcode 11.

Normally for old iOS versions the only option is to find a device on the used market that is still running that specific version. But it’s usually a waste of effort to try and support all point releases within a major release. Approximately everyone updates to the latest available, so for devices limited to iOS 13 (are there any? I don’t know) that would be 13.6 at the moment.

“Breakpoint 1.1” sounds like the debugger is stopping at a breakpoint you’ve set. Is there a blue arrow in the gutter on the left of your code where the line numbers are? That’s a breakpoint. You can drag it away to get rid of it. Or manage them using the breakpoints navigator in the left sidebar.

Playing audio is one of the few officially supported reasons to keep your app running in the background. Perhaps that’s what they’re using?

You can file an enhancement request using the Feedback & Bug Reporting link down at the bottom right, but don’t hold your breath. They are not known for great communication / responsiveness to developers.

Use a server to send your SMS or email. You can do whatever you want there.

Why are you reloading any rows? Don’t you just need to call setNeedsLayout on your cell’s content view? Or if you’re using auto layout you probably don’t even have to do that. Just adding/removing your subviews should work.

Apparently this is just a bug in iOS. Other posters have claimed you can safely ignore the warnings. Here’s a recent thread on it: https://developer.apple.com/forums/thread/651992