-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[PAID] Attachments - Unable to upload pdf file due to "Something went wrong" error #24275
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @dangrous ( |
regression from #20798 |
@mkhutornyi is right I think - @Julesssss do you have time to look at this to see if you can figure anything out? I'll keep checking too but looks like you'll be more familiar |
Hi, I reported this the day before this issue gets created. Will I get the reporting bonus? |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.51-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 2023-08-16. 🎊 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.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Sorry all I was out for the day at that point. |
I think so, it looks like you reported this 1 day earlier. |
Triggered auto assignment to @mallenexpensify ( |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.52-5 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-08-17. 🎊 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.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
@Santhosh-Sellavel I handled the comment, below, since it was pretty internal anyway. PR: #20798 Do you want to start the discussion in Slack? We don't need a regression test because this was already caught by our existing tests. Then we should be good to pay @bernhardoj for reporting, and @Santhosh-Sellavel for C+ review. Thanks! |
@Santhosh-Sellavel can you start the Slack discussion for this, and then we can pay and close out? Thanks! |
Started a discussion here Can I get a payment summary @mallenexpensify? |
@dangrous Can you assign a new BZ seems @mallenexpensify is OOO |
@Santhosh-Sellavel could you please double check if this is not re-introduced on |
@mountiny do you have a hunch that it is? |
@mountiny It's working fine on the main! Screen.Recording.2023-08-30.at.2.35.29.AM.mov |
bump! |
I'm going to work on payment for this and will have an update in a little bit. |
@bernhardoj - I have hired you to a reporting job via Upwork. I'll take another look tomorrow when I log back on. @Santhosh-Sellavel - I was on sabbatical so missed the manual requests payment going live, I'm still figuring that out but I'll do my best to get it done asap. |
@Santhosh-Sellavel - Did you already request payment via Newdot? If not, can you do that? That should make a GH for payment for you with manual requests. |
@strepanier03 Can you add a payment summary comment. So I can request on ND |
@strepanier03 accepted, thanks! |
It was just failing on one adhoc build, all good, thanks! |
@Santhosh-Sellavel - My apologies, I didn't realize that is what you were waiting for. In our SO instructions the request comes before the summary step so we were both waiting on the other. Summarizing payouts for this issue: Issue reporter: @bernhardoj - Paid $250 via Upwork - Contract ended and feedback left. Contributor: N/A - internal PR Contributor+: @Santhosh-Sellavel - $1000 to be paid via Manual Requests. |
@Santhosh-Sellavel - Once you send the request I'll assign to Jason for payment. |
Requested on ND |
Reviewed the details for @Santhosh-Sellavel. $1,000 payment approved via NewDot based on BZ summary. |
Got, thanks @JmillsExpensify! I will close this now, but if it needs to be reopened for any reason please comment and @ mention me so I can review. |
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:
Expected Result:
Preview of the file to be displayed
Actual Result:
Something went wrong screen blocker
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.51.0
Reproducible in staging?: Yes
Reproducible in production?: No
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6157877_RPReplay_Final1691505969.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: