@Scardfox hi, it is now fixed after submitting a ticket.

@Scardfox Same here. I sent a detailed bug report. I'll post on here again if they figure it out with a fix. Otherwise an update will surprise us.