I think we saw what you meant! We just posted a new update (Version 1.0.2) which should correct that problem. I managed to do it too, and it seems to be working in the new build!
