Hey @arpansac,
I understand this is a critical issue and we working with our engineering team to make sure we can provide a fix as soon as possible. However, I don’t have a timeline that I’m able to provide just yet.
In the meantime, you should be able to use version 1.8.6. My understanding is that this issue was introduced with version 1.9.0.
As using 1.8.5 or above is required, you can try using version 1.8.6 to see if that resolves the issue you’re seeing.
Let me know if that helps.
Thanks,
Max