Can confirm that this issue was fixed in 4.2.0-30.36, but it seems to be back again in the recent update to 4.2.0-32.37. Anyone else seeing that?
Can confirm that this issue was fixed in 4.2.0-30.36, but it seems to be back again in the recent update to 4.2.0-32.37. Anyone else seeing that?