-
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
[HOLD for payment 2024-08-02] [$250] Web - "Something went wrong" when trying to submit an expense that has an attached receipt #45967
Comments
Triggered auto assignment to @Beamanator ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
I can't reproduce on version v9.0.10-7, though after submitting the expense to someone, it gets put on Hold with a red brick road. |
Job added to Upwork: https://www.upwork.com/jobs/~017b5e835a2e35369b |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
I could not repro either, demoting: Screen.Recording.2024-07-23.at.09.18.01.mp4 |
ProposalPlease re-state the problem that we are trying to solve in this issue."Something went wrong" when trying to submit a manual expense after attaching a receipt to it What is the root cause of that problem?When we create a track-expense, the The problem is the
What changes do you think we should make in order to solve the problem?We should check if the
What alternative solutions did you explore? (Optional) |
@mountiny I can reproduce this bug. Here are the steps to reproduce:
|
Thanks @nkdengineer your proposal makes sense to me, I will assign you now |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Will raise the PR soon. |
I have updated the OP with the description from @nkdengineer |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
contributor details |
This comment was marked as off-topic.
This comment was marked as off-topic.
@rafaykr please review our community's Contributing documentation before continuing to post here :D |
ProposalPlease re-state the problem that we are trying to solve in this issue."Something went wrong" when trying to submit an expense that has an attached receipt #45967 What is the root cause of that problem?The policy ID of fake users is set to "_FAKE_" on registration as part of onboarding, which is not in the correct format for processing on tracking an expense. The constants for ID_FAKE and OWNER_EMAIL_FAKE are not in the correct format too - "_FAKE_" instead of "FAKE_". App/src/pages/home/ReportScreen.tsx Line 199 in ba8e2ad
What changes do you think we should make in order to solve the problem?The report policy ID should be set to "FAKE_" instead of "_FAKE_" on fake user registration/onboarding as well as the values for constants ID_FAKE and OWNER_EMAIL_FAKE. This resolves the issue for new fake users. All records of existing fake users require a migration to update their policy ids. The migration should rename existing policy ID values currently set to "_FAKE_" to "FAKE_" in the REPORT collection (e.g. in /src/libs/migrations/RenameReportPolicyID.ts). What alternative solutions did you explore? (Optional)N/A |
@mariapeever thanks so much for your proposal, but we already hired someone for this job about 10 hours ago. I'd recommend looking for the |
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.12-0 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-02. 🎊 For reference, here are some details about the assignees on this issue:
|
oh hey we need a bugzero person for payment here 😅 |
Triggered auto assignment to @slafortune ( |
@slafortune please help with payment here, I forgot to add the |
@fedirjh Role C+ - requires payment through NewDot Manual Requests $250 |
$250 approved for @fedirjh |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.10-6
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The app does not crash
Actual Result:
Notice that the app crashes after a few second
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6549951_1721682212879.A-42971.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @fedirjhThe text was updated successfully, but these errors were encountered: