Closed ruchernchong closed 3 weeks ago
This has been fixed in 3.1.3, upgrade to at least this version. If that's still an issue just reopen the issue
This has been fixed in 3.1.3, upgrade to at least this version. If that's still an issue just reopen the issue
Thank you for the prompt reply! I confirm that the error is now fixed for me!
Error:
Here is the reference for the error mentioned.
Of course, I can temporary fix it by using the suggested solution, but would be nice if this will also be gracefully fixed by the next release.