Ah, sorry - my mistake! OK, I see the issue, and it should be resolved in the 1.02 update, which just went up. Thanks for your patience!
