I asked to make sure. Yes, this has been reported. It seems like it's not exactly a bug. Looks more like a synchronization issue between the client and the server. The fact that its easily rectified via a simple reset of the app means that your local client just has to update with the missing data.
As I said though, I've added it to my report and I'll bring it to the dev's attention.