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
Currently, the contact images come from the local image server spun by status-go. This is great because it saves memory for images.
However, it makes it so that the image URL is always the same. Something like https://Localhost:46739/contactImages?publicKey=0x03c5ece7da362d31199fb02d632f85fdf853af57d89c3204b4d1e90c6ec13bb23c&imageName=thumbnail
So when the image gets updated in the DB, we get a signal from status-go that the contact got updated, but the URL is the same, so the comparison we do for the contact properties doesn't trigger an update (dataChanged).
The solution for that is to do similarly to this change done for communities, ie add a version query param:
Description
Currently, the contact images come from the local image server spun by status-go. This is great because it saves memory for images.
However, it makes it so that the image URL is always the same. Something like
https://Localhost:46739/contactImages?publicKey=0x03c5ece7da362d31199fb02d632f85fdf853af57d89c3204b4d1e90c6ec13bb23c&imageName=thumbnail
So when the image gets updated in the DB, we get a signal from status-go that the contact got updated, but the URL is the same, so the comparison we do for the contact properties doesn't trigger an update (
dataChanged
).The solution for that is to do similarly to this change done for communities, ie add a version query param:
Acceptance criteria
addTimestampToURL
is removed from the codeThe text was updated successfully, but these errors were encountered: