Skip to content
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

[$500] Split - App crashes when opening split preview in archived workspace chat #35176

Closed
6 tasks done
kbecciv opened this issue Jan 25, 2024 · 13 comments
Closed
6 tasks done
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors

Comments

@kbecciv
Copy link

kbecciv commented Jan 25, 2024

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: v1.4.32-2
Reproducible in staging?: y
Reproducible in production?: y
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: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Go to workspace chat.
  2. Create a manual split.
  3. Delete the workspace.
  4. Return to the workspace chat.
  5. Click on the split preview.

Expected Result:

App does not crash.

Actual Result:

App crashes.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6354999_1706207861404.20240125_235148__1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01dc3eb6e0c42b3468
  • Upwork Job ID: 1750598490050453504
  • Last Price Increase: 2024-01-25
@kbecciv kbecciv added External Added to denote the issue can be worked on by a contributor Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jan 25, 2024
@melvin-bot melvin-bot bot changed the title Split - App crashes when opening split preview in archived workspace chat [$500] Split - App crashes when opening split preview in archived workspace chat Jan 25, 2024
Copy link

melvin-bot bot commented Jan 25, 2024

Job added to Upwork: https://www.upwork.com/jobs/~01dc3eb6e0c42b3468

Copy link

melvin-bot bot commented Jan 25, 2024

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jan 25, 2024
Copy link

melvin-bot bot commented Jan 25, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)

@kbecciv
Copy link
Author

kbecciv commented Jan 25, 2024

We think that this bug might be related to #wave5-free-submitters
CC @dylanexpensify

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Jan 25, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

Split - App crashes when opening split preview in archived workspace chat

What is the root cause of that problem?

When we delete a workspace, we remove the policy from the collection as a result we cannot access it
And in this component we have an incorrect condition without an availability check isTaxTrackingEnabled in the policy

As result, we have an undefined for policy and then get error

const shouldShowTax = props.isPolicyExpenseChat && props.policy.isTaxTrackingEnabled;

What changes do you think we should make in order to solve the problem?

To fix this issue we can update conditions like
For example

const shouldShowTax = props.isPolicyExpenseChat && props.policy && props.policy.isTaxTrackingEnabled;

const shouldShowTax = props.isPolicyExpenseChat && props.policy.isTaxTrackingEnabled;

Or we can use lodash or something else

Similar condition we have for MoneyTemporaryForRefactorRequestConfirmationList

What alternative solutions did you explore? (Optional)

NA

@melvin-bot melvin-bot bot added the Overdue label Jan 29, 2024
Copy link

melvin-bot bot commented Jan 29, 2024

@stephanieelliott, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick!

@stephanieelliott
Copy link
Contributor

Hey @alitoshmatov looks like we have a proposal ready here, can you please review?

@melvin-bot melvin-bot bot removed the Overdue label Jan 30, 2024
@alitoshmatov
Copy link
Contributor

@ZhenjaHorbach Thank you for your proposal, your RCA is correct. The solution is straightforward and on point.

@alitoshmatov
Copy link
Contributor

We can go with @ZhenjaHorbach ' proposal.
@ZhenjaHorbach just make sure we are covering all similar cases for deleted policy

C+ reviewed 🎀 👀 🎀

Copy link

melvin-bot bot commented Jan 30, 2024

Triggered auto assignment to @jasperhuangg, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@mkhutornyi
Copy link
Contributor

#34072 should have handled this but they missed this as deprecated component.

But will be fixed in #29107

image

@alitoshmatov
Copy link
Contributor

Great, thank you @mkhutornyi .

Then we can close this issue or put it on hold

@ZhenjaHorbach
Copy link
Contributor

In fact, this problem is related to the crash
And the deletion ticket has not even been created yet and it is not known when this will happen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors
Projects
None yet
Development

No branches or pull requests

6 participants