We think we’ve fixed this issue with the Update to 0.58.0, just released. Thanks for the report, and let us know if you run into this sort of thing again!
We think we’ve fixed this issue with the Update to 0.58.0, just released. Thanks for the report, and let us know if you run into this sort of thing again!