It's very likely you experienced the issue that I have outlined in the image that is posted above ^
Really sorry for the inconvenience.
This one requires a client update to fix, so it would mean maintenance mode, QA testing, and then waiting for the App Store to process the update hoping it doesn't take a whole day.
We've fixed it locally, so our next version should squash this bug.