Mariusz Florek, do you still experience this error? We change some things in 5.1.0.Beta3 and it seems I cannot replicate the issue.
Could you confirm the this is working now?

Thanks