Hi, seems like this got fixed in v1.18 and the update should arrive in the next days/week. You can monitor the release here and you can find the fix mentioned in the release notes here.
I hope this will solve your issue 
4 Likes