The issue was resolved yesterday. We have created support ticket through Partner Center portal, and confirmed that it was an issue with latest build, and later it was resolved.