This content has been marked as final. Show 2 replies
1 of 1 people found this helpful
Thank you for reporting the issue. We acknowledge the problem and we are working on this. I will keep you posted with further updates.
This issue in not consistent to produce. It is fixed and will be part of next SDK release