search

rrbrambley / MessageBeast-Android

A library for building Message-based apps on App.net
MIT License
5 stars 0 forks source link

Location instances for unsent messages are sometimes not deleted #37

Closed rrbrambley closed 10 years ago

rrbrambley commented 10 years ago

For example, a DisplayLocationInstances may have two message ids for a location that only has one existing Message associated with it. My guess is that the display location instances are not properly being deleted when the unsent message is being deleted.

rrbrambley commented 10 years ago

New guess: display location is not populated on message when it gets deleted, so no display location instances are deleted. Perhaps relevant in the pending deletion case – the message is pulled from the DB right before deleting it, but the display location is not populated.

rrbrambley commented 10 years ago

I confirmed that performing a full sync actually sets the location instance count back to the correct amount.

rrbrambley commented 10 years ago

Should be fixed in 95027645dea8da2772754cb158ed209ce75cd1d1