See the comment made by @BlackDex in another post
As mentioned, this is an already reported upstream issue.