Here is the current status of my ticket referenced above: "Recent Similar Reports:Less than 10 Resolution:Open" Apple does not appear to make these tickets public, so you should file your own ticket in feedback assistant using "Printing" as the category, describing your crash, and collectively our similar tickets will increase the scope of this crash and hopefully get addressed by Apple after it gets deemed a priority.

Thanks for the workaround, this is working for me as well. Anyone using this code, keep in mind the following in the documentation when using the contactPrinter function: "Calling this method can take a significantly long time (up to 30 seconds)". Once Apple provides a real fix to this bug, we shouldn't have to depend on this, but this fixes it for our users in the meantime!

@manjitbhullar1 You can try this, but it pretty much looks like the examples already provided, perhaps you need to dispatch your code to a different thread? https://gist.github.com/rwyland/3dd3f8727effb92d554d773e11208286

An update from Apple, the status of my ticket is now: "Resolution: Potential fix identified - For a future OS update". So hopefully should see something in a beta build soon

I would like to note that the workaround I have in place that appears to resolve this issue is to create and reuse a single instance of UIPrinter for all print jobs (so try creating a static shared singleton). It appears that recreating a Printer with the URL every job is causing issues with the delegate, leading to extra large printing.