I have the same problem and I wonder if this started to happen the moment when one of the internal testers tried using the public link. Have you come to any resolution on this?

Same here (Czech Republic). My address contains diacritics and after the error message on that input field, removing diacritics > submitting, I see that Apple changes the chars, e.g. from "s" to "sh" where š would normally be. Submitting the corrected by them variant leads to the same error. I wrote to finance with the error flow description and referring to this thread. [Update] Reply from the Finance came instantly with the following solution that worked: Hello, Please attempt to make this update from the Agreements tab, and not the banking tab.  From the AGREEMENTS tab, click on the paid agreement’s name that requires a banking update. Examples are “Paid Apps”, “Paid Books”, “Music”, “Video”, etc. You have to click the words (agreement name) even though they do not have a blue hyperlink. You must be on the AGREEMENTS tab, not the Banking Tab Under Bank Accounts on the AGREEMENTS tab, scroll to the right and click Edit From the Edit drop down menu select from: Edit Current Account Update your bank account holder address  If the message asks you to verify your banking, click SAVE again. If the message persists, please click save 3 times. Please be sure to let the page refresh before you click it again.  This should resolve the issue.

Only brainstorming here: Lock can be hold by the serialization iterator and then on other thread some other code might have tried to change the array? Iterator might have panicked. Or vice versa. Only my speculative speculation. And this is on the main thread, iOS might have considered that is not a "resolvable" lock and killed you at once. If you do read-write access to this array, try to serialize it via, e.g. the queue?

Same here. Says 8 days to me. Was sending yesterday without any warning.

My payment with the same due date was delayed until Jan 3rd 2022. Company payment came at Dec 31rd, as expected, so I know it is hardly Apple who caused the delay. Looks like "usual" New Year (and any other holiday) bank mess here, in Czech Republic. And then banks have the nerves to back date these in the statements, as if nothing happened. Fingers crossed for your payment to appear soon.

These 4 years of not fixing this issue is probably a silent statement from Apple that it works as designed.

Same here.

Thank you glow! Indeed. This would explain the problems I'm seeing. I redesigned the screen to only have one Paste control on it and it is placed in the dedicated cell with only a help label below it. Even when sizing that dedicated UIPasteControl - until it stopped "touching" the neighbour controls, it was asking for the permission. I can see the point in avoiding obscuring its parts. How can we define the UIPasteControl sizing requirements properly to be sure to give it enough space? I'm trying its intrinsic size and it always returns as zero rect. I'm trying to achieve its size predictability via minimumContentSizeCategory and maximumContentSizeCategory, so it has a predictable size for the different accessibility text sizes. What's the correct way of placing/sizing this control in a storyboard with auto layout? The example here: https://developer.apple.com/documentation/uikit/uipastecontrol?changes=_5 Suggests: pasteButton.frame = CGRect(x: view.bounds.width/2.0, y: view.bounds.height/2.0, width: 150, height: 60) Is it something considered the safe dimensions for the UIPasteControl for all of the accessibility text sizes? Width of 150 doesn't seem to be "safe" - the whole UIPasteControl may not be even shown or it might be raising the permission alert, if the control itself shows. Is it something that needs to be embedded into SwiftUI? Or would it work well in some sort of a container like UIStackView, would this one size it properly for all of the accessibility text sizes? Some pointers would be appreciated so we can build future-proof designs that would not break easily.

Same thing here, with different selector names.

In my case (Dell 40" with thunderbolt/usb hub) it was me tweaking the power management settings earlier and then all usb ports being down after OS update every time mac book went into sleep and woke up. sudo  pmset restoredefaults and restart helped for good.

As I understand, it should be a bug with Xcode and App Store Connect. You better create a feedback for Apple. See the related thread: https://developer.apple.com/forums/thread/714736?answerId=727968022#727968022

Be sure to report it to Apple.

Same here. What worked for me was to remove the preview part from the code, save. Added it back and it all worked.

Not working for me as well. I have swift+objc codebase, not sure if this can be the reason.

Didn't work for most of Wednesday, then started to work Thursday morning (CET) for me. And now, Thursday evening CET it is not working again. I see the new build in the Testflight, but after a spinning circle on UPDATE/INSTALL it returns to the non-installed, non-updated status.