Still seeing this issue in 12.2. Following the workaround sometimes corrects it, but not on all devices.
Rory Hinnen
Still seeing this issue in 12.2. Following the workaround sometimes corrects it, but not on all devices.