Ok the new build for v2.3.1 is up and should have the fix! Let me know if you still experience this issue and thanks again for reporting it
Thanks for the report, I'm on it! pushing a new build soon :)
