You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-08-19] [$250] LHN – Concierge chat opens when change priority mode to Most recent #46110
👋 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:
Identify the pull request that introduced this issue and revert it.
Please re-state the problem that we are trying to solve in this issue.
User navigates to Concierge chat
What is the root cause of that problem?
When the onboarding data is changed we resolve the onboarding value here. If we log in with a new account and complete the onboarding flow and then isOnboardingFlowCompleted the second time, isOnboardingFlowStatusKnownPromise promise will return the onboarding data to the old data because after we complete the onboarding flow, the onboarding data is changed and we don't reset the isOnboardingFlowStatusKnownPromise promise.
It leads isLoadingApp changing and this useEffect is triggered again. As I explained above because the onboarding data is the old data onNotCompleted callback is called and the navigation state is reset. Then the concierge chat is opened as the recent chat.
📣 @olya-ivanochko! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
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:
[@DylanDylann] The PR that introduced the bug has been identified. Link to the PR: NA
[@DylanDylann] 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: NA
[@DylanDylann] 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: NA
[@DylanDylann] Determine if we should create a regression test for this bug. Yes
[@DylanDylann] 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.
Activity
melvin-bot commentedon Jul 24, 2024
Triggered auto assignment to @arosiclair (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 24, 2024
👋 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:
lanitochka17 commentedon Jul 24, 2024
We think that this bug might be related to #vip-vsp
francoisl commentedon Jul 24, 2024
Hm interestingly, it doesn't happen if you already have multiple chats or rooms. Doesn't seem like something worth blocking for, going to demote.
nkdengineer commentedon Jul 25, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
User navigates to Concierge chat
What is the root cause of that problem?
When the onboarding data is changed we resolve the onboarding value here. If we log in with a new account and complete the onboarding flow and then
isOnboardingFlowCompletedthe second time,isOnboardingFlowStatusKnownPromisepromise will return the onboarding data to the old data because after we complete the onboarding flow, the onboarding data is changed and we don't reset theisOnboardingFlowStatusKnownPromisepromise.App/src/libs/actions/Welcome.ts
Line 178 in b0f810d
The problem happens when we change the priority mode from
focustorecent, we have a logic here to call theOpenAppAPI again.App/src/libs/actions/App.ts
Lines 72 to 76 in b0f810d
It leads
isLoadingAppchanging and thisuseEffectis triggered again. As I explained above because theonboardingdata is the old dataonNotCompletedcallback is called and the navigation state is reset. Then the concierge chat is opened as the recent chat.App/src/libs/Navigation/AppNavigator/createCustomBottomTabNavigator/BottomTabBar.tsx
Lines 59 to 63 in b0f810d
What changes do you think we should make in order to solve the problem?
We should reset the
isOnboardingFlowStatusKnownPromisepromise when the onboarding data is changedApp/src/libs/actions/App.ts
Lines 72 to 76 in b0f810d
What alternative solutions did you explore? (Optional)
Or we can revert the change in this PR #45327 to use an
onboardingvariable and update it every time the onboarding data changes.App/src/libs/actions/App.ts
Lines 72 to 76 in b0f810d
39 remaining items
olya-ivanochko commentedon Aug 19, 2024
There were regressions fixed by other contributors:
#46110 (comment)
#46110 (comment)
melvin-bot commentedon Aug 19, 2024
📣 @olya-ivanochko! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
mallenexpensify commentedon Aug 20, 2024
@DylanDylann , @nkdengineer , can you confirm if there are regressions on this issue? See one revert after staging in the PR. Thx
nkdengineer commentedon Aug 20, 2024
@mallenexpensify We had a regression on this issue and I fixed it here. All revert PRs were closed.
mallenexpensify commentedon Aug 21, 2024
Thx @nkdengineer per CONTRIBUTING.md
Contributor: @nkdengineer paid $125 via Upwork
Contributor+: @DylanDylann paid $125 via Upwork.
@DylanDylann plz complete the BZ checklist above. , thanks
DylanDylann commentedon Aug 21, 2024
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:
[@DylanDylann] The PR that introduced the bug has been identified. Link to the PR: NA
[@DylanDylann] 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: NA
[@DylanDylann] 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: NA
[@DylanDylann] Determine if we should create a regression test for this bug. Yes
[@DylanDylann] 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.
Regression Test Proposal
Do we agree 👍 or 👎
DylanDylann commentedon Aug 26, 2024
Not overdue. Waiting for @mallenexpensify
mallenexpensify commentedon Aug 26, 2024
Thanks @DylanDylann , all set!