We did something that should have fixed this issue for the next build. So we'll see what happens then. :)
