Forums
(@nathanaelhoun)
3 years, 2 months ago
Hi @gsarig, I can confirm that upgrading to 1.3.2 fixed the issue. Thanks a lot for your work and your update!