Thank you all for being persistent about this issue. We've taken a deeper look and have indeed discovered a minor bug in our code. It's fixed now and should be getting out to all of you in one of our next releases.
Many apologies for this annoying inconvenience!
