This should now be fixed in version 1.2.8.3.
Please let me know if this is the case on your end.
Once again, thank you for the report and sorry for the inconvenience.
This should now be fixed in version 1.2.8.3.
Please let me know if this is the case on your end.
Once again, thank you for the report and sorry for the inconvenience.