Sorry for the lack of updates on this. We have been able to replicate the issue, but in a slightly different way (and in a non-deterministic way). We're still investigating and unfortunately we have not any fix or workaround yet, but we will try to address this issue as soon as possible. Thanks
|