Okay, turns out this issue is the reason for this behaviour. This workaround works until the next update.