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

[HOLD for payment 2023-10-30] [HOLD for payment 2023-10-27] [$250] Login - App crash on login #29965

Closed
2 of 6 tasks
kbecciv opened this issue Oct 19, 2023 · 31 comments
Closed
2 of 6 tasks
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@kbecciv
Copy link

kbecciv commented Oct 19, 2023

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: 1.3.87.1
Reproducible in staging?: y
Reproducible in production?: n
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: @gadhiyamanan /Applause- Internal team reported later
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697694190199399

Action Performed:

  1. Logout if you logged in
  2. Create new account
  3. Enter email which is not used before and enter magic code

Expected Result:

App should 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

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2023-10-19.at.11.15.49.AM.mov
MacOS: Desktop
Screen.Recording.2023-10-19.at.11.18.06.AM.mov

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0110ec104becd93e90
  • Upwork Job ID: 1715007628320174080
  • Last Price Increase: 2023-10-19
  • Automatic offers:
    • hoangzinh | Reviewer | 27283181
    • gadhiyamanan | Reporter | 27283182
    • situchan | Contributor | 27283230
@dukenv0307
Copy link
Contributor

Proposal

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

App crash on login

What is the root cause of that problem?

After login with a new account ReportActionsView is rendered with reportActions as an empty object briefly

image

And then the app crashes with this condition because reportActions is {}

const iouRequestActions = reportActions?.filter((action) => action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU && iouRequestTypes.includes(action.originalMessage.type)) ?? [];

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

We should safely using _.filter instead of using reportActions?.filter

const iouRequestActions = _.filter(reportActions, (action) => action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU && iouRequestTypes.includes(action.originalMessage.type))

const iouRequestActions = reportActions?.filter((action) => action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU && iouRequestTypes.includes(action.originalMessage.type)) ?? [];

What alternative solutions did you explore? (Optional)

@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Oct 19, 2023
@melvin-bot melvin-bot bot added the Daily KSv2 label Oct 19, 2023
@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Oct 19, 2023
@OSBotify
Copy link
Contributor

👋 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:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@melvin-bot
Copy link

melvin-bot bot commented Oct 19, 2023

Triggered auto assignment to @robertjchen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@situchan
Copy link
Contributor

situchan commented Oct 19, 2023

@dukenv0307 It's intentional to get rid of _ in TS.

After login with a new account ReportActionsView is rendered with reportActions as an empty object briefly

We should fix this root cause. So there should be no case of reportActions being set to non-array.

@mountiny mountiny added the External Added to denote the issue can be worked on by a contributor label Oct 19, 2023
@melvin-bot melvin-bot bot changed the title Login - App crash on login [$500] Login - App crash on login Oct 19, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 19, 2023

Job added to Upwork: https://www.upwork.com/jobs/~0110ec104becd93e90

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 19, 2023
@mountiny mountiny changed the title [$500] Login - App crash on login [$250] Login - App crash on login Oct 19, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 19, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Oct 19, 2023

Upwork job price has been updated to $250

@chiragkcodes
Copy link

Proposal

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

App crashes on first login of user.

What is the root cause of that problem?

ReportScreen.js is loading props from Onyx (WithOnyx).
reportActions data is loaded after OpenReport action is called.
During first user login, no reportActions are present due to other action calls being executed(e.g. BeginSignIn, SignInUser,OpenApp), which delays the call to OpenReport action (sequencial)
During this time, Onyx is loading reportActions as an object (Not sure if this is right behavior for Onyx)

When getMostRecentIOURequestActionID gets called during first render of ReportScreen, reportActions is still an object here.

const iouRequestActions = reportActions?.filter(.....

Since, filter() is not defined on object, the app is crashing.

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

We need to override reportActions in ReportScreen.js
First we will rename the property reference of reportActions to _reportActions.
This way we wont have to touch existing references of reportActions.

function ReportScreen({
    betas,
    route,
    report,
    reportMetadata,
    reportActions: _reportActions,
   ...

Then within component we will define new local variable which will take care of overriding wrong value (i.e. object to array)

const reportActions = _.isArray(_reportActions)? _reportActions : [];

I tested after these changes, app is not crashing anymore.

What alternative solutions did you explore? (Optional)

Need to investigate why Onyx is loading reportActions as object in the first place.
I believe this will need some deep-dive on react-native-onyx package.

@kubabutkiewicz
Copy link
Contributor

@mountiny PR with the fix

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Hourly KSv2 labels Oct 19, 2023
@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 19, 2023
@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Oct 19, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 19, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@mountiny
Copy link
Contributor

@situchan $250 for review and testing
@gadhiyamanan $50 for reporting

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Oct 20, 2023
@melvin-bot melvin-bot bot changed the title [$250] Login - App crash on login [HOLD for payment 2023-10-27] [$250] Login - App crash on login Oct 20, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 20, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 20, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot
Copy link

melvin-bot bot commented Oct 20, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.87-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-10-27. 🎊

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.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

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:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot
Copy link

melvin-bot bot commented Oct 20, 2023

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:

  • [@situchan] The PR that introduced the bug has been identified. Link to the PR:
  • [@situchan] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • [@situchan] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • [@situchan] Determine if we should create a regression test for this bug.
  • [@situchan] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@stephanieelliott] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@mallenexpensify
Copy link
Contributor

I'm still getting a crash on login on staging and the PR for/from here already hit staging.

  1. Log in
  2. App crashes

or... try to navigate from a report link to staging.new.expensify.com and it crashes

or... more reliable repro steps
from my mallen@expensifail.com account, try to open mallen@expensify.com to chat with.

Happening on Mac - Chrome and Windows - Chrome (via browserstack)

2023-10-20_14-47-08.mp4
2023-10-20_14-46-26.mp4

@situchan
Copy link
Contributor

@mallenexpensify it would be helpful if you can share console log on web

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Oct 23, 2023
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2023-10-27] [$250] Login - App crash on login [HOLD for payment 2023-10-30] [HOLD for payment 2023-10-27] [$250] Login - App crash on login Oct 23, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 23, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.88-11 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-10-30. 🎊

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.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

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:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot
Copy link

melvin-bot bot commented Oct 23, 2023

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:

  • [@situchan] The PR that introduced the bug has been identified. Link to the PR:
  • [@situchan] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • [@situchan] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • [@situchan] Determine if we should create a regression test for this bug.
  • [@situchan] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@stephanieelliott] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed Weekly KSv2 labels Oct 27, 2023
@melvin-bot
Copy link

melvin-bot bot commented Oct 30, 2023

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

@mountiny
Copy link
Contributor

@mallenexpensify could you please share console logs with that crash?

@melvin-bot melvin-bot bot removed the Overdue label Oct 30, 2023
@situchan
Copy link
Contributor

@mallenexpensify could you please share console logs with that crash?

It's different crash - #30109

@stephanieelliott
Copy link
Contributor

Is there a regression? Or are we all good to pay here? cc: @mallenexpensify

@mountiny
Copy link
Contributor

mountiny commented Nov 1, 2023

@stephanieelliott I think we are good to pay @situchan suggested its a different issue

@stephanieelliott
Copy link
Contributor

Summarizing payment on this issue:

  • Issue reporter: @gadhiyamanan $50 -Upwork - PAID
  • Contributor: N/A
  • Contributor+: @situchan $250 - Upwork - PAID

Upwork job is here, no bonus is included on final payout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests