Metadata of conversation members seems to be saved/duplicated at a second point in the database / not invalidated from cache on change
Summary
Metadata of conversation members seems to be saved/duplicated at a second point in the database / not invalidated from cache on change.
Example: after changing a user's profile picture (or, as reported also the name), the old picture (and name?) of the moment of the conversation's creation are still being returned by the /api/conversations
endpoint.
Steps to reproduce
- Change your profile picture
- Request
/api/conversations
endpoint - Compare the returned picture with your new one
What is the current bug behavior?
Old data seems to be stored and returned.
What is the expected correct behavior?
Always return the current user metadata from central store.
Relevant error messages and/or screenshots
Possible fixes
Always pull fresh conversation member information instead of storing them / caching them. If already cached, make sure to invalidate cache on user upload / profile change.