Closed NoreddineRadi closed 1 year ago
I think it has a relation with the last version "3.0.0". I don't have the error with this version 2.4.2
Hello, I have encountered the same problem. Have you solved it
Hi, I didn't find a solution for the latest version : "3.0.0" but you can use the oldest version 2.4.2, in that case the error disappears.
Hi, someone has already found a fix for this issue?
Same here. The funny thing is, it was working just fine yesterday. Today simply refuses to work.
@robmosca thanks for addressing the Issue 👏🏼 Do you know when we can expect to have a new deployed version with this bug fix?
Hi @rdlagemann, I am not a maintainer unfortunately. I would suggest you write to the #maintainers channel in Slack. Based on my previous experience, releases on this package do not happen very often.
This has been released. Closing the issue.
I think it has a relation with the last version "3.0.0". I don't have the error with this version 2.4.2