Sorry that this is still happening. I believe I've fixed this in my current build (for the next update), but I will do lots of testing to verify it's definitely been resolved!
