Looking back, I see evidence of this behavior going back to the beginning of February. Version 3.10.0 for iOS came out January 31st so I assume this bug started with that update. It's not consistent so the app might appear to work correctly some of the time. I'm not sure--I don't usually look a...