I tested the latest MAC driver, 5.7.2, and all is good now. I tested it on Catalina and Mojave and it printed to the highest priority tray with letter size paper each time I tested it. I had put 11X17 paper in tray 1 and it NEVER asked for letter size paper in tray 1 once.
I certainly encourage you and anyone else to try to get traction on this issue Andrew. My log number will now show as being closed because it was declined. I pressed this until I got a Teams meeting with the driver development team. The result of that meeting was to encourage users to contact Apple if they want to see this resolved in macOS Catalina. I'll DM you my final log number.
What log number or SPAR number were you givem for this. I will encourage other analysts to add their escalations to this SPAR so as to put a little pressure on the driver engineers to come up with an official Xerox driver. We are seeing this more and more as customers update their MACs.
I haven't updated this post but I did look into this extensively and another forum member confirmed that my current solution works for them. You can see the details in my response to their post found here.
I am having no luck with the new driver, either. In fact, I think the problem is worse because I can't even specify another tray besides Tray 1. Called local dealer. Was told Apple broke it so they'll have to fix it. Called Xerox and after a long period of time the agent said I needed to call my local dealer. Meanwhile, specs for my machine (D-125) still claim it works with Catalina. Not true. Not true at all. I have an old machine running *Classic*. Guess I'll try to print a pdf from that. This is not acceptable.
A trusted coworker of mine tells me that the new macOS driver that just released on the support site (Version 5.5.9) resolves this issue. I spent the day working in a Windows environment so I haven't been able to validate this myself yet. But if you are experiencing this issue install the new driver. If you're navigating the Xerox support site you may still find the old version listed for Catalina. Change the dropdown to Mojave (10.14) and you'll see it. Here's a direct link and on the side of the page you'll see that it is supported on macOS 10.13-10.15.
I have started a log with Xerox and I'll update this post when we come to an eventual conclusion. For now my best recommendation is to either edit the CUPS configuration on each workstation to change the default tray to one that contains 8.5x11 (A4 outside of the US) paper or connect to the printer with Airprint if that is supported by the model. I looked at a packet capture that I took and it is clear that the job properties are specifying tray 1, when auto select was picked, so the machines are responding as they should.
I too am experiencing a ton of issues with 5.5.2 driver and Tray 1 across multiple platforms. Hoping there's an update to the issue as I have 3 customers that are anxiously awaiting a fix.
My coworkers from across the nation have been reporting issues with macOS Catalina and the current macOS Xerox driver that causes all print jobs to specify tray 1 when "Auto Select" is specified in the macOS Paper Feed dialog box. I have validated this issue personally using macOS 10.15.5 when printing to a Versalink C7030, Altalink C8045, and a C70. I confirmed that Airprint submissions are not affected by this issue. Machines that do not have 2 tandem letter trays are less likely to notice this issue because tray 1 is often configured with letter size paper. With tray 1 configured with a size other than letter sized paper a new driver installation and subsequent print job, with default settings, will get held for resources. Changing the CUPS default for "Paper Tray" under the Paper Output section does change the tray that the jobs default to but it does not correct the behavior of Auto Select.
I'm currently on hold to start a log for this issue and the message keeps talking about this forum, so I figured that I would get this post up while I'm on hold. I can only test on my Macintosh that is running 10.15.5 (including the supplemental update) but I have heard reports of this occurring on versions of macOS back to 10.15.3. In almost all instances users are reporting that the driver worked as intended until they updated macOS to a newer version.
Solved! Go to Solution.