That's rather odd. While we're not quite sure how to replicate that bug (let alone why it's doing that), we'll try to find ways to mitigate it in the next update.
I'm completely clueless to how it happened too. Maybe it's just that it's a mobile bug?