-
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 2023-05-25] [HOLD for payment 2023-05-23] [Feature] Support all file types for attachments #11189
Comments
Triggered auto assignment to @kevinksullivan ( |
Current assignee @kevinksullivan is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Triggered auto assignment to @neil-marcellini ( |
Current assignee @neil-marcellini is eligible for the Engineering assigner, not assigning anyone new. |
Hmm is this a front end only error? What do you think @Santhosh-Sellavel? |
We have frontend restrictions but could be a backend too as per this comment Lines 16 to 18 in 3780e0f
|
Thanks for looking into that! I think we should make this internal since I imagine most of the work will be on the backend. |
The timing for this is super tight so I'm going to add the |
Draft PRs created and it's working nicely for me locally. PRs should be ready for review on Monday! |
PR reviewed and merged!! 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.14-14 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 2023-05-23. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.15-12 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 2023-05-25. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
@youssef-lr quick question on this issue: Should it still be open? |
Further, @rushatgabhane have been paid you out for this one? I see you reviewed one of the linked PRs. |
I think we can close! |
Alrighty! |
@rushatgabhane please reach out over New Expensify if anything remains outstanding for you. |
I paid Rushat on New Dot |
Thanks! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Try to upload a CSV, XLSX, HEIF or HEFV image. None of them work!
Expected Result:
We should support all file types, especially since we have an antivirus scanner handling all attachments.
Actual Result:
The upload files with the following error message.
Workaround:
No workarounds
Platform:
Version Number: 1.2.2-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): Everyone
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1663790246088889
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: