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
after update userinfo,the conversation info isn't change.
such as i changed the faceurl or showname, the userinfo is trully changed,but the conversation info which contains faceURL and showname isn't changed as userinfo.
i trully saw the userinfo reserved in server is change. i can't find where conversation info reserved.
mybe the client sdk reserved in local? im not sure.
How to reproduce
1、just change with official admin web page , and the sdk awlays returns the first time i used info.
2、then have a see on mongodb,find this userinfo,it trully changed
3、just open the app,use the client sdk get conversation, and conversation always returns the firts time faceurl and showname i setted.
Version information
Device: e.g. iPhone X
OS: e.g. iOS 14.7.1
Package Version: e.g. v3.8+2
Flutter Version: e.g. v3.7.0
The text was updated successfully, but these errors were encountered:
i tried uninstall the app, and it works. so the problem is in client sdk, it cache in local, and when the server changes any info, it never have chance to change,right?
Describe the bug
after update userinfo,the conversation info isn't change.
such as i changed the faceurl or showname, the userinfo is trully changed,but the conversation info which contains faceURL and showname isn't changed as userinfo.
i trully saw the userinfo reserved in server is change. i can't find where conversation info reserved.
mybe the client sdk reserved in local? im not sure.
How to reproduce
1、just change with official admin web page , and the sdk awlays returns the first time i used info.
2、then have a see on mongodb,find this userinfo,it trully changed
3、just open the app,use the client sdk get conversation, and conversation always returns the firts time faceurl and showname i setted.
Version information
The text was updated successfully, but these errors were encountered: