Thanks. We already fixed this on our website, and will be fixed in the app in version 1.2 (version 1.1 was already submitted for review).