Everything is back to normal. Thanks to the Apple team for fixing this issue.

It appears that Swiss banks are affected. How can this issue be resolved? Who should we contact to get help? We were planning to finish development of a new app and enjoy our Christmas holidays, but now payouts are blocked and we don’t know how to resolve this issue.

In the email “Reject Payment Notification,” there is a “Contact Us” link at the bottom, but the contact form is not working. It is not possible to select a “Content Type” or a “Topic.” Therefore, it is not possible for us to contact the responsible team. Unfortunately, we have still not received any response to our email to App Store Connect Support. Is there really no Apple employee who can help us here? This is a serious issue.

Is there an Apple employee who can help us with this issue? Our business bank account is with UBS Switzerland and has been registered in App Store Connect for over five years. All payouts have worked without any issues during this time. App Store Connect has now suddenly marked the account as invalid, even though nothing has changed and the account is fully functional. A payout from Google Play was credited to this account today. We temporarily added a private account, removed the UBS account, and then added it again. However, the error message in App Store Connect remains unchanged. We need payouts to continue going to this account, as our accounting and business processes depend on it. Other business accounts exist but are used for different purposes. The error message refers to an incorrect “routing number”. However, when adding a Swiss bank account, there is no routing number field. Instead, a bank clearing number is required. We selected this number using App Store Connect’s search, and it matches our UBS account details exactly. All entered information is correct. This appears to be an internal App Store Connect bank account validation issue. A failed transfer cannot be the cause of this error, as the payout window has not yet been reached. The next transfer should only occur at the end of December or in January. We have already contacted Apple Developer Support but have not yet received a response. Any assistance from an Apple employee or confirmation of a known issue would be greatly appreciated. Thank you.

Our payment information is also marked as active in the business data. The message is in the “Payments and Financial Reports” section.

I believe that our bank had maintenance today and the payment may have been rejected due to a technical error. When logging into online banking, it says that online banking will not be available tonight due to maintenance. Is there a way to trigger the payout to the same account again on Monday? Or will it only be attempted once we have added a new account? Unfortunately, there is no clear information about this.

We were able to reproduce this issue. Deleting a 48 MP RAW image in DNG format consistently fails on iOS 26.1. After this occurs, the iPhone must be restarted before any other images can be deleted again. Deleting 24 MP RAW or 48 MP JPEG images works without any issues. This behavior was observed on an iPhone 15 Pro Max running iOS 26.1. The issue requires urgent attention and resolution. When the same 48 MP RAW image is transferred via AirDrop to a device running iOS 18.6, it can be deleted there without any issues.

Since iOS 26, our users have also been experiencing this issue. Unfortunately, we can't find a solution on our side. On some devices, the completionHandler is never called, and afterward, you can no longer perform any operations on PHPhotoLibrary.

We’re unable to use our custom photo picker either, because when the user denies full photo access, the system displays a dialog to select specific images. Unfortunately, touch input doesn’t work properly there either, making it impossible to select any images.

We just tested it. Unfortunately, it hasn't changed. It looks like we'll have to switch to our own photo picker for iPad apps on macOS.

Several users reported this issue to us yesterday, so we tested it ourselves. We confirmed that there is a problem selecting images in all of our apps running as iPad apps on macOS 26.0.1. We’ve been investigating potential solutions, but unfortunately, we haven’t found one yet.

The problem seems to have been fixed in iOS 26. We no longer see any crashes in the new system.

It also works on older iOS versions.

Our solution: swift: if UIDevice.current.userInterfaceIdiom == .pad { textField.keyboardType = .numbersAndPunctuation } objective-c: if([UIDevice currentDevice].userInterfaceIdiom == UIUserInterfaceIdiomPad) { self.textField.keyboardType = UIKeyboardTypeNumbersAndPunctuation; }

Yes, we see a lot of crashes like this in our apps, too. But we can't reproduce it. OS Version: iPhone OS 18.6 (22G86) Release Type: User Baseband Version: 2.70.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Reason: *** -[__NSSingleObjectArrayI objectAtIndex:]: index 2 beyond bounds [0 .. 0] Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: OurAppName [72412] Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1950500c0 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x1924e9abc objc_exception_throw + 88 (objc-exception.mm:356) 2 CoreFoundation 0x1950418c8 -[__NSSingleObjectArrayI objectAtIndex:] + 308 (NSSingleObjectArray.m:18) 3 PrintKitUI 0x1f34d4518 -[UIPrintPaperSizeOption listItemSelected:] + 88 (UIPrintMoreOptions.m:896) 4 PrintKitUI 0x1f34a0a0c -[UIPrintOptionListViewController tableView:didSelectRowAtIndexPath:] + 116 (UIPrintOptionCells.m:103) 5 UIKitCore 0x198b902fc -[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:isCellMultiSelect:deselectPrevious:performCustomSelectionAction:] + 1184 (UITableView.m:9365) 6 UIKitCore 0x198b90620 -[UITableView _userSelectRowAtPendingSelectionIndexPath:animatedSelection:] + 256 (UITableView.m:9419) 7 UIKitCore 0x198b9072c -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 216 (UITableView.m:9438) 8 UIKitCore 0x1978b984c -[_UIAfterCACommitBlock run] + 72 (_UIAfterCACommitQueue.m:137) 9 UIKitCore 0x1978b9784 -[_UIAfterCACommitQueue flush] + 168 (_UIAfterCACommitQueue.m:228) 10 UIKitCore 0x19783e254 _runAfterCACommitDeferredBlocks + 260 (UIApplication.m:3284) 11 UIKitCore 0x19783df74 _cleanUpAfterCAFlushAndRunDeferredBlocks + 80 (UIApplication.m:3262) 12 UIKitCore 0x19783de84 _UIApplicationFlushCATransaction + 72 (UIApplication.m:3325) 13 UIKitCore 0x19783de0c __setupUpdateSequence_block_invoke_2 + 336 (_UIUpdateScheduler.m:1659) 14 UIKitCore 0x19783d404 _UIUpdateSequenceRun + 84 (_UIUpdateSequence.mm:136) 15 UIKitCore 0x19783cab4 schedulerStepScheduledMainSection + 208 (_UIUpdateScheduler.m:1173) 16 UIKitCore 0x1978381e4 runloopSourceCallback + 92 (_UIUpdateScheduler.m:1341) 17 CoreFoundation 0x194f4592c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1970) 18 CoreFoundation 0x194f45744 __CFRunLoopDoSource0 + 172 (CFRunLoop.c:2014) 19 CoreFoundation 0x194f455a0 __CFRunLoopDoSources0 + 232 (CFRunLoop.c:2051) 20 CoreFoundation 0x194f45f20 __CFRunLoopRun + 840 (CFRunLoop.c:2969) 21 CoreFoundation 0x194f47adc CFRunLoopRunSpecific + 572 (CFRunLoop.c:3434) 22 GraphicsServices 0x1e1d6d454 GSEventRunModal + 168 (GSEvent.c:2196) 23 UIKitCore 0x197969274 -[UIApplication _run] + 816 (UIApplication.m:3845) 24 UIKitCore 0x197934a28 UIApplicationMain + 336 (UIApplication.m:5540) 25 OurAppName 0x102a2a4dc main + 76 (main.m:16) 26 dyld 0x1bb9d9f08 start + 6040 (dyldMain.cpp:1450)