Has this happened since the 2.8.14 app update? That should have fixed it, and I can't reproduce the issue now.