We regret for the inconvenience caused.
We are still working on this mentioned issue fix, due to its complexity we unable to include this fix in our 2019 Volume 1 SP1 release. We are working on this issue fix with high priority. We will fix this issue and include the issue fix in our upcoming weekly NuGet release update, it will be available by May 28, 2019. We appreciate your patience until then.
Subburaj Pandian V