Thank you for the report.
That’s weird but I can’t reproduce it at the moment. There may be a device-dependent issue.
It could be related to this issue but I don’t know:
I’ll consider adding a feature for debugging as it’s not helpful just seeing the error message on this issue.