Skip to content

[Due for payment 2025-04-10] [Due for payment 2025-04-08] [$250] Start chat - Start chat page is broken after refreshing the page #59352

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

Closed
1 of 8 tasks
jponikarchuk opened this issue Mar 31, 2025 · 27 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor

Comments

@jponikarchuk
Copy link

jponikarchuk commented Mar 31, 2025

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: 9.1.21-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Other

Action Performed:

Precondition:

  • Browser is Mac Chrome.
  • Expensify desktop app is installed.
  1. Go to staging.new.expensify.com
  2. Create a workspace if there isn't one.
  3. Open FAB > Start chat > Chat.
  4. Refresh the page.
  5. Do not interact with "Open New Expensify" modal first.

Expected Result:

Start chat page will open Chat page.

Actual Result:

Start chat page opens Room page. The tabs disappear. "Description" label input overlaps with the entered text.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6784750_1743110346795.Dvnb8264_1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021906720830415317384
  • Upwork Job ID: 1906720830415317384
  • Last Price Increase: 2025-03-31
  • Automatic offers:
    • brunovjk | Reviewer | 106732122
    • nkdengineer | Contributor | 106732123
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @stephanieelliott
@jponikarchuk jponikarchuk added Bug Something is broken. Auto assigns a BugZero manager. DeployBlockerCash This issue or pull request should block deployment labels Mar 31, 2025
Copy link

melvin-bot bot commented Mar 31, 2025

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

Copy link

melvin-bot bot commented Mar 31, 2025

Triggered auto assignment to @JS00001 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

@melvin-bot melvin-bot bot added the Daily KSv2 label Mar 31, 2025
Copy link

melvin-bot bot commented Mar 31, 2025

💬 A slack conversation has been started in #expensify-open-source

@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Mar 31, 2025
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.

@JS00001
Copy link
Contributor

JS00001 commented Mar 31, 2025

I'm able to repro in staging, looking into it

@JS00001
Copy link
Contributor

JS00001 commented Mar 31, 2025

This looks like the exact same bug as #59223 (comment), which had its fix reverted, I don't think this is a deploy blocker

@nkdengineer
Copy link
Contributor

nkdengineer commented Mar 31, 2025

🚨 Edited by proposal-police: This proposal was edited at 2025-03-31 14:01:30 UTC.

Proposal

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

Start chat page opens Room page. The tabs disappear. "Description" label input overlaps with the entered text.

What is the root cause of that problem?

It comes from #59156

isSidePaneTransitionEnded has the default value is true then, the input can be focused immediately while the transition isn't completed because isScreenTransitionEnded is updated to true. In this case, the transition from OnyxTabNavigator breaks and the bug appears.

const [isSidePaneTransitionEnded, setIsSidePaneTransitionEnded] = useState(true);

setIsScreenTransitionEnded(isSidePaneTransitionEnded);

ref={inputCallbackRef}

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

We should change the default value to false like we did here for useAutoFocusInput

const [isSidePaneTransitionEnded, setIsSidePaneTransitionEnded] = useState(true);

We also should only update isScreenTransitionEnded if shouldHideSidePane is changed

const prevShouldHideSidePane = usePrevious(shouldHideSidePane);
useEffect(() => {
    if (!shouldHideSidePane || prevShouldHideSidePane) {
        return;
    }

    setIsScreenTransitionEnded(isSidePaneTransitionEnded);
}, [isSidePaneTransitionEnded, shouldHideSidePane, prevShouldHideSidePane]);

setIsScreenTransitionEnded(isSidePaneTransitionEnded);

Optional: Since we already use shouldDelayFocus and autoFocus prop, we can remove inputCallbackRef to prevent multiple focus can trigger.

ref={inputCallbackRef}
inputID={INPUT_IDS.ROOM_NAME}
isFocused={isFocused}
shouldDelayFocus
autoFocus
/>
</View>
<View style={styles.mb5}>

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

@nkdengineer
Copy link
Contributor

@JS00001 It's a blocker, another change caused this now.

@brunovjk
Copy link
Contributor

brunovjk commented Mar 31, 2025

I reviewed the PR, can we assign me as C+ here? Thanks.

@blazejkustra
Copy link
Contributor

We should change the default value to false like we did here for useAutoFocusInput

const [isSidePaneTransitionEnded, setIsSidePaneTransitionEnded] = useState(true);

@brunovjk if this fixes it, I think this is way to go!

@JS00001 JS00001 added the External Added to denote the issue can be worked on by a contributor label Mar 31, 2025
Copy link

melvin-bot bot commented Mar 31, 2025

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

@melvin-bot melvin-bot bot changed the title Start chat - Start chat page is broken after refreshing the page [$250] Start chat - Start chat page is broken after refreshing the page Mar 31, 2025
@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Mar 31, 2025
Copy link

melvin-bot bot commented Mar 31, 2025

Current assignee @brunovjk is eligible for the External assigner, not assigning anyone new.

Copy link

melvin-bot bot commented Mar 31, 2025

📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

@nkdengineer
Copy link
Contributor

@brunovjk The PR is ready for review.

@brunovjk

This comment has been minimized.

@brunovjk
Copy link
Contributor

brunovjk commented Apr 1, 2025

PR on staging. Should we CP @mountiny ?

@mountiny
Copy link
Contributor

mountiny commented Apr 1, 2025

its going there

@mountiny mountiny removed the DeployBlockerCash This issue or pull request should block deployment label Apr 1, 2025
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Apr 1, 2025
@melvin-bot melvin-bot bot changed the title [$250] Start chat - Start chat page is broken after refreshing the page [Due for payment 2025-04-08] [$250] Start chat - Start chat page is broken after refreshing the page Apr 1, 2025
Copy link

melvin-bot bot commented Apr 1, 2025

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

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Apr 1, 2025
Copy link

melvin-bot bot commented Apr 1, 2025

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.21-3 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 2025-04-08. 🎊

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Apr 1, 2025

@brunovjk @stephanieelliott @brunovjk The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Apr 3, 2025
@melvin-bot melvin-bot bot changed the title [Due for payment 2025-04-08] [$250] Start chat - Start chat page is broken after refreshing the page [Due for payment 2025-04-10] [Due for payment 2025-04-08] [$250] Start chat - Start chat page is broken after refreshing the page Apr 3, 2025
Copy link

melvin-bot bot commented Apr 3, 2025

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

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Apr 3, 2025

@brunovjk @stephanieelliott @brunovjk The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

@brunovjk
Copy link
Contributor

brunovjk commented Apr 7, 2025

BugZero Checklist:

  • [Contributor] Classify the bug:
Bug classification

Source of bug:

  • 1a. Result of the original design (eg. a case wasn't considered)
  • 1b. Mistake during implementation
  • 1c. Backend bug
  • 1z. Other:

Where bug was reported:

  • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
  • 2b. Reported on staging (eg. found during regression or PR testing)
  • 2d. Reported on a PR
  • 2z. Other:

Who reported the bug:

  • 3a. Expensify user
  • 3b. Expensify employee
  • 3c. Contributor
  • 3d. QA
  • 3z. Other:
  • [Contributor] 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: Fix auto focus after side pane is closed, fix popover position on attachment modal #59156 (comment)

  • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

  • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

Regression Test Proposal

Test:

Precondition:

  • Desktop app is installed
  1. Create a workspace if we don't have
  2. Open FAB > Start chat
  3. Refresh the page
  4. Verify that the start chat page isn't broken

Do we agree 👍 or 👎

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Apr 8, 2025
@stephanieelliott
Copy link
Contributor

stephanieelliott commented Apr 9, 2025

Summarizing payment on this issue:

Upwork job is here: https://www.upwork.com/jobs/~021906720830415317384

@stephanieelliott
Copy link
Contributor

Testrail case is here: https://github.com/Expensify/Expensify/issues/489079

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 External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests

7 participants