Can confirm this issue was resolved in 3.3.0
↧
Can confirm this issue was resolved in 3.3.0