-
Notifications
You must be signed in to change notification settings - Fork 3k
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-19] [$500] No feedback and delay when uploading a large attachment #38478
Comments
Triggered auto assignment to @Christinadobrzyn ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.When uploading a large attachment there is a delay on iOS. What is the root cause of that problem?Image picker library is taking time to fetch the result on IOS. To test it out, I had added logs to check time inside The time difference was coming between call to Github issue for some discussion on the same: react-native-image-picker/react-native-image-picker#2117 What changes do you think we should make in order to solve the problem?Add const imagePickerOptions = {
includeBase64: false,
saveToPhotos: false,
selectionLimit: 1,
includeExtra: false,
+ assetRepresentationMode: 'current'
}; |
Job added to Upwork: https://www.upwork.com/jobs/~01398c6a10dbc0b325 |
I can reproduce this. Here's the GH about increasing the size from 24 MB - #32702 I think this can be external |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh ( |
Proposal |
@hoangzinh Kindly have a look at my proposal when possible. |
Hi @ShridharGoel I don't think you have a correct RCA. When I put console log in that |
@hoangzinh If you are using a Simulator, are you able to replicate the issue? |
ah nope I can't. Is it only reproducible in a real iphone? |
@hoangzinh It seems like that. I've analysed the issue more - it's related to the image picker taking time. I'll update my proposal. |
Proposal |
@Christinadobrzyn @ShridharGoel what is the file size you used to test? I used a video file with 128MB but it shows up file size error almost immediately |
@hoangzinh Do you have access to a physical iPhone to check? |
Yes I do @ShridharGoel |
@hoangzinh Can you check with a 500 MB video maybe? @situchan Do you have an iPhone? If possible, can you check if you are able to replicate this? |
@ShridharGoel I can test on my iPhone. Can you attach or share link to video file you tested? |
I am seeing "Attachment too large" modal immediately |
testing this again, I am also seeing the "attachment too large" prompt immediately. So I think this is resolved but I'm just double-checking with @neil-marcellini to make sure this is what is expected. RPReplay_Final1711332264.MP4 |
@Christinadobrzyn that looks like a slightly different flow you tested. I'm consistently able to reproduce with this video, regardless of network speed. I'm on iOS 17.3.1, New Expensify v1.4.50-5 IMG_6440.MOV |
@Christinadobrzyn I've been looking into this HEIC issue today. For now it seems like there's a mime type conversion happening for those images at some time. Conversion is a pretty standard approach for the HEIC format, but with |
@Christinadobrzyn the PR is ready, I'll try to complete the recordings later this evening or tomorrow, but since the heic is being treated as a file attachment on other platforms, this should be ready for review. To sum up - the manual conversion worked and they indeed had an incorrect magic bytes signature in comparison to the file extension. |
Awesome! Thank you so much @BrtqKr! |
update for Melvin - PR is under review - @hoangzinh do you have a update on the PR review? |
The PR is still reviewing. I reported a bug in the PR and waiting for a fix. Hopefully, we can merge it this week. |
monitoring PR #46025 - let us know if you have any other updates @hoangzinh |
PR has been merged and waiting deploy to staging |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.18-10 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-19. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payouts due - can we confirm this is the correct payment for this job?
Do we need a regression test for this @hoangzinh? |
@Christinadobrzyn, yep I think we need. I will complete BZ checklist soon |
Regression Test ProposalOn IOS/Android:
On Web/Desktop/mWeb:
Do we agree 👍 or 👎 |
BugZero Checklist:
|
Awesome! Thanks @hoangzinh. Regression test - https://github.com/Expensify/Expensify/issues/421516 This is payment day and there are no regressions so paying this out based on this payment summary Closing! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @neil-marcellini
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1710524006372329
Action Performed:
Expected Result:
"Attachment too large Attachment size is larger than 25 MB limit" popup shows immediately
Actual Result:
Nothing happens for quite a while, then you receive a popover explaining that the attachment is too large
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
RPReplay_Final1710521379.MP4
IMG_6440.MOV
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Christinadobrzyn / @ChristinadobrzynIssue Owner
Current Issue Owner: @puneetlath / @ChristinadobrzynThe text was updated successfully, but these errors were encountered: