fix: use image clock when updating profile images to cause re-render #21830
+15
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jenkins BuildsClick to see older builds (8)
|
alwx
approved these changes
Jan 10, 2025
|
Merged this one because the PR is a duplicate of a PR that was already tested and merged to the release branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attention
cc @alwx
fixes #21787
Summary
clockvalue to the identity images that are returned by status-go, because for some reason the clocks are defaulted to0.Platforms
Areas that maybe impacted
Functional
Steps to test
WIP
Before and after screenshots comparison
After Changes on iOS
Screen.Recording.2024-12-12.at.09.29.39.mov
status: ready