We have finally found a solution for this problem. Where it works, we load the UIImage from a JPG file. Where it doesn't work, the UIImage is created programmatically. The solution is to convert the UIImage to JPEG data and then create a new UIImage for printing. With this new UIImage, printing finally also works on a Mac in an iPad app. UIImage *imageToPrint = [UIImage imageWithData:UIImageJPEGRepresentation(originalImage, 1)];

And an html string can be printed using a UIGraphicsBeginPDFContextToData. The disadvantage is that you have to define a fixed page size, but it prints with this solution in an iPad app on the Mac. - (NSData *)createPDFfromHTML:(NSString *)htmlString { UIMarkupTextPrintFormatter *formatter = [[UIMarkupTextPrintFormatter alloc] initWithMarkupText:htmlString]; UIPrintPageRenderer *pageRenderer = [[UIPrintPageRenderer alloc] init]; [pageRenderer addPrintFormatter:formatter startingAtPageAtIndex:0]; NSMutableData *pdfData = [NSMutableData data]; CGRect paperRect = CGRectMake(0, 0, 595.3, 841.9); // A4 CGRect printableRect = CGRectInset(paperRect, 72, 72); // 1-inch margins UIGraphicsBeginPDFContextToData(pdfData, paperRect, nil); [pageRenderer setValue:[NSValue valueWithCGRect:paperRect] forKey:@"paperRect"]; [pageRenderer setValue:[NSValue valueWithCGRect:printableRect] forKey:@"printableRect"]; NSInteger pages = [pageRenderer numberOfPages]; for (NSInteger i = 0; i < pages; i++) { UIGraphicsBeginPDFPageWithInfo(paperRect, nil); [pageRenderer drawPageAtIndex:i inRect:paperRect]; } UIGraphicsEndPDFContext(); return pdfData; } - (void)printHtmlTest { NSString *htmlContent = @"<h1>Hello World</h1>"; NSData * pdfData = [self createPDFfromHTML:htmlContent]; UIPrintInteractionController *printController = [UIPrintInteractionController sharedPrintController]; printController.printingItem = pdfData; UIViewController *controller = [[UIViewController alloc] init]; [printController presentAnimated:YES completionHandler:^(UIPrintInteractionController *printInteractionController, BOOL completed, NSError *error) { // }]; }

It turns out that our solution is not really a solution. It works with a single image, but not always. If we print multiple images on one page or on multiple pages, it doesn't work on the Mac. It doesn't matter whether we convert the images to JPG beforehand or not. It seems to be a timing problem. If we don't do anything in drawPageAtIndex, the print preview always appears. If we do a lot in drawPageAtIndex, the print preview doesn't appear on the Mac. It worked in earlier macOS versions. It always works on the iPhone and iPad. Unfortunately, we haven't been able to find a solution. It would be ideal if we had the option to only draw something in drawPageAtIndex when the print preview is already displayed. We have the instance method printInteractionControllerDidPresentPrinterOptions. This is called a moment before the print preview has actually been displayed. But we could set a flag from this method with a delay of perhaps one second so that something should only be drawn in drawPageAtIndex from then on. However, we are missing the option to restart the drawing in the print preview using the programming code. If, for example, the print orientation is changed manually in the print preview dialog, then drawPageAtIndex is called again and everything is drawn correctly. Does anyone know a way to restart the drawing in drawPageAtIndex of the UIPrintPageRenderer from the programming code?

With macOS 15 Sequoia, printing in the iPad app works without any problems.

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)

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

It also works on older iOS versions.

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

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.

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.

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.

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 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.

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.

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