We are aware of this bug that is affecting some of our users in v1.5. We have submitted an update that fixes this to Apple. It will be out after the review process. Sorry for the inconvenience. This bug is fixed in v1.5.1.