hi @kenedyt,
A fix version (3.5.1) has now been released.
Our apologies for the issues surrounding 3.5.0
Hi @kenedyt ,
Thanks for raising, we have located the issue and we are now working on releasing version 3.5.1 which will resolve the issue in 3.5.0.
We anticipate that the new release should be ready in the next hour.
Hi @kenedyt ,
Sorry for the late reply and thank you for raising this with us.
We are already working on a fix for this. Its almost done and we will have a new version released as soon as possible.
As soon as the new version is released we will update you accordingly.
