-
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 2022-04-13] [$750] When clicking on Room Settings after workspace deleted, error displayed - reported by @Santhosh-Sellavel #8033
Comments
Triggered auto assignment to @alex-mechler ( |
This is certainly something that we should handle better. Sending external |
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Triggered auto assignment to @marcochavezf ( |
Ah, I didn't catch this! Upwork job here. |
Oh, hm.. @TomatoToaster has this been fixed then? CC: @Santhosh-Sellavel |
not really, I have an old account which I delete the workspace before this was solved. so I think this issue will appear on developer accounts only they delete workspace on development mode before this gets fixed. |
The problem does not appear in the latest ProposalThis happen because the object App/src/pages/ReportSettingsPage.js Line 156 in 34e2d3e
- const linkedWorkspace = _.find(this.props.policies, policy => policy.id === this.props.report.policyID);
+ const linkedWorkspace = _.find(this.props.policies, (policy) => {
+ if (policy === null) {
+ return false;
+ }
+
+ return policy.id === this.props.report.policyID;
+ }); Before changesScreen.Recording.2022-03-13.at.11.47.40.movAfter changesScreen.Recording.2022-03-13.at.11.48.07.mov |
We mostly try to fix the root cause of the problem before patching the code. I will wait to see more proposals that can identify why this line creates an issue and works sometimes. This issue has been reported a few times earlier and this line creates the issue but why? And which policies have null data. |
@parasharrajat It's because there are some App/src/libs/actions/Policy.js Lines 142 to 153 in 9dbfbf1
|
Ok, I see. Did you run some actions which resulted in this Onyx state or does it already has null values? But that said, I have already faced this issue earlier and I know that #8033 (comment) fixes this crash as suggested earlier https://expensify.slack.com/archives/C01GTK53T8Q/p1643191135467000 I would be curious to know why are we storing null values in the Onyx. that seems like the real issue. |
Also, I like to point out that I reported this issue a month back from this issue https://expensify.slack.com/archives/C01GTK53T8Q/p1643191135467000. And there was a +1 on that. I don't why it wasn't ported to GH. cc: @trjExpensify |
Looking at that original convo @parasharrajat, Applause and Aldo weren't able to reproduce it with the steps provided? |
@parasharrajat, I too think the job should be assigned to @mollfpr because that's the only fair thing to do. We will discuss this further internally in the upcoming days. How to address this kind of situation in the future, thanks! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.51-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 2022-04-13. 🎊 |
Triggered auto assignment to @laurenreidexpensify ( |
Triggered auto assignment to @dylanexpensify ( |
👋 I'm OoO next week (so is @laurenreidexpensify, I believe), so reassigning for another CM to handle the payment after the regression period. Thanks, @dylanexpensify! Upwork job is here: https://www.upwork.com/jobs/~01c95cafe702e5684f |
You got it tom! |
@parasharrajat sent offer to accept and pay you out as C+! @Santhosh-Sellavel please apply to this job to be paid for reporting the issue! |
@mollfpr payment sent, contract ended! |
@dylanexpensify done! |
Offer sent @Santhosh-Sellavel! |
Alrighty! Everyone has been paid, contracts ended, posts removed! 🎉 |
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:
Open Settings Page for the room
Actual Result:
Error Page Appeared
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.40-1
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43995119/157184784-9e5bedd9-107d-4c3d-a8b4-97c0ca2bb4e0.mov

Upwork job URL: https://www.upwork.com/jobs/~01c95cafe702e5684f
Issue reported by: @Santhosh-Sellavel
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1645738088150939
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: