Skip to content

[Due for payment 2026-01-05] [Due for payment 2025-12-30] Accounting - Netsuite set up steps are not highlighted correctly #78096

Closed

Description

@jponikarchuk

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: v9.2.82-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #71868
Email or phone of affected tester (no customers): ndk.2303+154@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 Home/Chrome
App Component: Workspace Settings

Action Performed:

Precondition: Create a control workspace and enable Accounting

  1. Open https://staging.new.expensify.com/
  2. Navigate to workspace setting
  3. Click on Accounting
  4. Click on Connect at 'Netsuite'
  5. Click 'Next' four times
  6. Click 'Back' four times

Expected Result:

Steps are highlighted correctly when going connection flow with Netsuite

Actual Result:

Step 5, at Credentials steps, Step 1 is highlighted.
Step 6. Steps 1 is highlighted and then there is no step is highlighted

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @VictoriaExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 19, 2025
  2. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    Triggered auto assignment to @VictoriaExpensify (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.

  3. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 19, 2025

    @github-actions
    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.
  6. nyomanjyotisa commented on Dec 19, 2025

    @nyomanjyotisa
    Member

    Proposal

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

    Accounting - Netsuite set up steps are not highlighted correctly

    What is the root cause of that problem?

    InteractiveStepSubHeader always initializes with startStepIndex={0}, but the actual current step is tracked in screenIndex from useSubStep

    <InteractiveStepSubHeader
    ref={ref}
    startStepIndex={0}
    stepNames={CONST.NETSUITE_CONFIG.TOKEN_INPUT_STEP_NAMES}
    />

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

    We can pass the current screenIndex to InteractiveStepSubHeader so it reinitializes with the correct step

                        startStepIndex={screenIndex}

    We could also fix the typo in CONST.NETSUITE_CONFIG.TOKEN_INPUT_STEP_NAMES where step 2 is '2,' instead of '2'

    TOKEN_INPUT_STEP_NAMES: ['1', '2,', '3', '4', '5'],

    What alternative solutions did you explore? (Optional)

    None

  7. francoisl commented on Dec 19, 2025

    @francoisl
    Contributor

    Thanks for the proposal.

    I confirmed that reverting #71868 fixes the issue. Since the #70746 only happened on mobile and it's pretty rare to connect to accounting on mobile, I think it's better to revert the PR in this case, and then do a proper follow-up that also addresses this issue.

    cc @abzokhattab @Pujan92

  8. 3 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 23, 2025
  10. changed the title [-]Accounting - Netsuite set up steps are not highlighted correctly[/-] [+][Due for payment 2025-12-30] Accounting - Netsuite set up steps are not highlighted correctly[/+] on Dec 23, 2025
  11. melvin-bot commented on Dec 23, 2025

    @melvin-bot

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

  12. melvin-bot commented on Dec 23, 2025

    @melvin-bot

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

  13. melvin-bot commented on Dec 23, 2025

    @melvin-bot

    @francoisl @VictoriaExpensify 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]

  14. changed the title [-][Due for payment 2025-12-30] Accounting - Netsuite set up steps are not highlighted correctly[/-] [+][Due for payment 2026-01-05] [Due for payment 2025-12-30] Accounting - Netsuite set up steps are not highlighted correctly[/+] on Dec 29, 2025
  15. melvin-bot commented on Dec 29, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.87-7 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 2026-01-05. 🎊

  16. melvin-bot commented on Dec 29, 2025

    @melvin-bot

    @francoisl @VictoriaExpensify 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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions