@DawidJanczak it was the same bug. Nikita already fixed it. It will work fine in 1.3.0 - expect a release soon.
1.3.0