ok. so unfortunately this looks like something that was fixed between 1.30.x and 2.0.0x