We were able to reproduce the mentioned issue at our end. We have confirmed that the issue is a defect and logged a defect report on this. The fix for the issue is estimated to be available on February 21st, 2019.
NSNick ShepherdFebruary 24, 2019 02:26 AM UTC
Any news on a resolution of this issue?
Mageshyadav MFebruary 25, 2019 10:33 AM UTC
Sorry due to internal network problem, we are unable to generate local nuget packages with the fix changes hence we will deliver the fix changes in our 2019 Volume 1 release which may be available in mid of March 2019.