I had this problem too a few times but have not come across it since v.0.1.6 update. Maybe it has been bug fixed?
