> I can also confirm on my side that 2.0.4 fixes the issue.

Nice, thanks for the feedback!

Reply via email to