You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I modify a ChatUser's photo for User A from a device, the ChatChannelController on an other device connected to User B inside a chat with User A will emit a change.
What did you expect to happen?
Live update for imageUrl inside ChatChannelView
What happened instead?
However, MessageContainerView (the default implementation of the ViewFactory) will cache the ChatUser's url in MessageCachingUtils, so the view's body will be recalled, but MessageAvatarView will be provided with the cached url.
This is done on prupose at the moment for performance reasons. Updating the image of a user will trigger a message update for almost every message, which in SwiftUI will cause a performance penalty.
Since updating the image is not a common action, the compromise of not live updating is okay for now. When you open the channel again, it will update.
For now, we do not have plans to change this, but we will re-open the issue if we decide to change this in the future.
What did you do?
If I modify a ChatUser's photo for User A from a device, the ChatChannelController on an other device connected to User B inside a chat with User A will emit a change.
What did you expect to happen?
Live update for imageUrl inside ChatChannelView
What happened instead?
However, MessageContainerView (the default implementation of the ViewFactory) will cache the ChatUser's url in MessageCachingUtils, so the view's body will be recalled, but MessageAvatarView will be provided with the cached url.
GetStream Environment
GetStream Chat version:
GetStream Chat frameworks: StreamChat, StreamChatSwiftUI
iOS version:
Swift version:
Xcode version:
Device:
Additional context
The text was updated successfully, but these errors were encountered: