Once again, thank you for taking the time to report this @krievinshj!
This should now be fixed with 1.3-beta2.
Please don’t hesitate to let us know if you experience any more trouble with this, by responding to this thread.
1 Like