We've fixed this properly in the build we just pushed, so it should work as it did before, without the workaround, now. Sorry about that!
