This has already been fixed.
I also confirmed that the proposed workaround does in fact address the problem for those using version 3.3 until 3.3.1 is released.
This has already been fixed.
I also confirmed that the proposed workaround does in fact address the problem for those using version 3.3 until 3.3.1 is released.