-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-08-14] [$250] Feature Request: When uploading, automatically reduce the size of receipt image if greater than 24mb #44084
Comments
Triggered auto assignment to @OfstadC ( |
|
Triggered auto assignment to Design team member for new feature review - @dannymcclain ( |
Is this a suggestion to implement a feature where our app reduces the file size of a local image before uploading? 🤔 Either way, I don't think we should do this. File size limits are SUPER common amongst all the apps I use daily, and I've never once seen any of them try to reduce a file's size for me (also, 24mb is a pretty generous size limit). I think we should leave this responsibility on the user personally. cc @Expensify/design for thoughts. |
Just for reference- This is step backwards from what OldApp does. I can upload a picture from my camera no problem on OldApp, I have to resize it myself on NewDot. I thought as a user this is a UX oddity. |
@AndrewGable are the normal photos your phone takes more than 24mb? I only ask because that seems reaaaaally big. Most of the photos on my phone (that I've taken) are around 1–3mb. |
How does OldDot handle this? Does it automatically resize the photo? |
Yes, it will allow the user to upload this receipt and OldApp will resize it for the user to allow upload. |
Oh I see, it's because you're shooting in Raw. But anyhoo! That's neither here nor there I suppose.
Thinking about it more, Figma does do something similar if you try to drop in a super mega image: it resizes it in the background, adds the resized image, and gives you a little message that tells you Figma resized the image. I think I'd be open to an approach like that where we just do it behind the scenes automatically (and maybe provide some indication that we've done it?) but I'd like to avoid this becoming like a whole user-flow centered around resizing an image before upload. That's what I though was originally being proposed, which is why I was not into it at first. |
Agree! I just think we should support cases that we did in the past, uploading a receipt from my phone's camera is one of those cases. |
Nice, that sounds good to me. Thanks for talking it out! |
Yeah. I actually think resizing the image automatically would be super neat cause just a warning is a blocking action. This isn't one of those scenarios where they'd want fine controls on image quality etc, they just wanna upload a receipt. I also don't like the idea of having the user having to resize or do it themselves through a UI, so I'm all for automatically doing this. |
100% agree Jon! |
So based on this conversation, @Expensify/design @AndrewGable would you all be comfortable updating this feature request to:
This would mean there would be no change in the UI. The user likely wouldn't even know we did it—but their receipt image would be uploaded smoothly with no issues. Note I think this would only apply to receipt image uploads—NOT images uploaded as attachments in chats |
Yes - That sounds great! |
Thanks team! 😃 - Added to Wave Collect and posted in Slack |
Job added to Upwork: https://www.upwork.com/jobs/~01b098d2eb27081851 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra ( |
@dannymcclain, @OfstadC, @luacmartins, @shubham1206agra, @nkdengineer Still overdue 6 days?! Let's take care of this! |
I'm investigating the PR. |
@nkdengineer Did something blocking you? |
@shubham1206agra we have a open PR here |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.17-2 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 2024-08-14. 🎊 For reference, here are some details about the assignees on 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:
|
Hey team! I had to send you new offers in Upwork. Please accept your relevant offer below so I can issue payment. Thank you 😃 |
Payment Summary@shubham1206agra paid $250 via Upwork |
Still pending - @nkdengineer please add a note here once the new offer is accepted so I don't miss it 😃 |
@OfstadC Thanks 🙇 I have accepted the offer |
Updated payment summary. This is just waiting on [@shubham1206agra] Please propose regression test steps to ensure the new feature will work correctly on production in further releases. @shubham1206agra can we get an update by EOD? Thanks! |
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:
|
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @AndrewGable
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1718830152208309
Problem:
Unable to upload an image taken from the camera because it’s larger than 24MB
Solution:
Option to reduce the size on device before uploadingContext/Examples/Screenshots/Notes:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @OfstadCThe text was updated successfully, but these errors were encountered: