known issue, will be fixed in v0.12.2