I have the same issue - the same MacBook Pro (2019) Intel i9 processor as the original post. I didn't notice it was caused by the simulator but it makes sense as I use the simulator for work all the time. I am not interested in a workaround. I am not sure I understand why that's not fixed already