Yamaha Steinberg USB ASIO Problems Since July Commit

I have a tester reporting problems with their Yamaha Steinberg USB ASIO device.
The issue is that the device usually fails to open, either when trying to reload settings or selecting it from the “Device” box in the audio settings panel.

Looking at the log file, there’s a whole host of ASIO error reported:

27 Oct 2019 16:47:10  ASIO: found Yamaha Steinberg USB ASIO
27 Oct 2019 16:47:10  ASIO: opening device: Yamaha Steinberg USB ASIO
27 Oct 2019 16:47:10  ASIO: closed
27 Oct 2019 16:47:10  ASIO: opening device: Realtek ASIO
27 Oct 2019 16:47:10  ASIO: 2 in, 6 out
27 Oct 2019 16:47:10  ASIO: 1024->1024, 1024, 0
27 Oct 2019 16:47:10  ASIO: setting default sample rate
27 Oct 2019 16:47:10  ASIO: error: setting sample rate - Not Present
27 Oct 2019 16:47:10  ASIO: Rates: 44100 48000 88200 96000 176400 192000
27 Oct 2019 16:47:10  ASIO: getLatencies() failed
27 Oct 2019 16:47:10  ASIO: creating buffers (dummy): 4, 1024
27 Oct 2019 16:47:10  ASIO: Latencies: in = 3211, out = 3211
27 Oct 2019 16:47:10  ASIO: device open
27 Oct 2019 16:47:10  ASIO: clock: Internal clock (cur)
27 Oct 2019 16:47:10  ASIO: rate change: 0 to 44100
27 Oct 2019 16:47:10  ASIO: disposing buffers
27 Oct 2019 16:47:10  ASIO: creating buffers: 8, 1024
27 Oct 2019 16:47:10  ASIO: channel format: 17
27 Oct 2019 16:47:10  ASIO: Latencies: in = 3211, out = 3211
27 Oct 2019 16:47:10  ASIO: starting
27 Oct 2019 16:47:13  ASIO: no callbacks - stopping..
27 Oct 2019 16:47:13  ASIO: closed
27 Oct 2019 16:47:13  *** ERROR: AudioDeviceManager init: Device didn't start correctly

I’ve dug through the commits and the only ASIO related addition between the last working build and the broken builds is this:

Which explicitly specialises some behaviour around the “Yamaha Steinberg USB ASIO”. It sounds like this is causing the problems.

Can you remember exactly what this was trying to fix? I don’t have a device to test with so this is a tricky one to debug. Any suggestions welcome…

It was added in response to this thread:

I’ll have another look today and see what it was fixing exactly.

Can I request that this change be reverted?
I’m getting more and more support tickets related to this now as users upgrade.

I don’t have a Steinberg IO to test with so can’t offer up much more by way of an alternative fix.
Perhaps @highcarbschwabe can check if reverting the change is still causing problems?

It seems odd this hasn’t been a problem in previous versions for us.
Were there specific steps to replicate it?