Closed vetalgo closed 9 months ago
@vetalgo investigating now
@vetalgo I believe this bug is fixed in v3.0.3 but I cant say for sure without knowing more about your environment.
If you get a second please update the package and lmk the result.
Thanks!
I believe this bug is now fixed as v3.0.3
Anyone who experiences the behaviour please reopen.