Avatar consistency issue

@MattJ @XaviFP On which side could this belong?

Going to say Converse.js of course ;)

Any chance the messages with no avatars were sent while you were not connected to the room, and the latest one was while you were connected?

Yes, it is

At least it should be easy to reproduce then. The fix is definitely on the Converse.js side though.

I'm not sure if this is exactly the same issue or not, but here is what I'm experiencing: on one message I see my avatar, and on another one I see the default avatar:

community.startinblox.com-1615018668194.log

This kind of issue usually happen when there is a Prosody restart.

Logs are telling us that Converse reached the timeout.

Anything we can do about it?

@manv Do you have some track for this kind of issue?