This issue has been fixed in v2.01.09 which we are getting close to releasing.
A potential work around is described here: