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
{{ message }}
Repository navigation
[Due for payment 2026-04-16] [Image][$1000] Improve NewDot image uploading experience, add large file support #9402
The image should be grayed (opacity 0.6 i.e., chatItemUnsentMessage) until its uploaded and once its uploaded it should not show the white thumbnail with loader
and instead continue showing the local thumbnail or show the final image immediately.
Actual Result:
The local image is being uploaded and we see the local thumbnail,
The local image has finished uploading and now we attempt to render it which first shows up a white thumbnail with loader
The render completes and we see the uploaded image
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Closing out this issue. The initial PR for uploaded image caching is on production and we are following up with the second issue here. Payment issue here.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.54-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@parasharrajat] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Jun 11, 2022
Triggered auto assignment to @MitchExpensify (
External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.MitchExpensify commentedon Jun 13, 2022
Upwork Job
706 remaining items
Julesssss commentedon Mar 18, 2026
Closing out this issue. The initial PR for uploaded image caching is on production and we are following up with the second issue here. Payment issue here.
melvin-bot commentedon Apr 9, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.54-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-04-16. 🎊
For reference, here are some details about the assignees on this issue:
[-][Image][$1000] Improve NewDot image uploading experience, add large file support[/-][+][Due for payment 2026-04-16] [Image][$1000] Improve NewDot image uploading experience, add large file support[/+]melvin-bot commentedon Apr 9, 2026
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
melvin-bot commentedon Apr 9, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Apr 10, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.