Hi,
first of all, please refer to this post for a workaround.
Second, indeed, things did not go in an optimal fashion here. With two core developers being unavailable during QA of Core Update 167, and a mixture of issues sounding to be related, the severity of this one completely fell through the cracks. 
Apologies for the inconveniences, and best regards,
Peter Müller