In T160233#2320961, @Geez wrote:

Hello everyone.
The issue has been resolved internally and the fix will appear in one of the upcoming updates.
Regards,
Geez