Hi,
I am also experiencing the same issue (and can confirm this is not fixed in the latest version), and all of our devs are moving to M1's in the next weeks.
Is there a ticket that can be tracked to be notified when this issue is resolved? (because I will have to find a work-around until then)