This is still occurring. Any progress?
I have the same issue and it still exists in 1.14.60. Does Fix Version/s 1.15.0.56 Beta mean that a fix has been made in the beta which will be in an upcoming stable release?
This is still occurring. Any progress?