I had someone else report that and it was fixed in the 0.1.1 minor update.
I was using the web browser one, so idk if that was updated or not. I will reread it again at some point in the next couple of days
It was updated to 0.1.1 too.