After some additional testing on our latest internal build, the issue seems to have disappeared. It was never marked as fixed so I’m not yet sure when the actual fix happened. This means I’m not sure when it’ll be fixed in a Binary build but it should be coming.