+1. We are also having this issue. The above workarounds didn't fix it for us either.

+1