K.Mitamura
Results
2
comments of
K.Mitamura
@gatapia No, unfortunately we did not find a workaround.
This issue seems to have been fixed in v2.13.0.