I'm happy to announce that this issue should hopefully be fixed in the new release V1.11!
If that turns out not to be the case, please feel free to reach out to us again.
