Hi there!

Thanks for the heads up! Yes, we were able to replicate this issue and have reported it to the development team. We are hoping to have this issue resolved patched in an upcoming build update.


Best,

Jerry