[$250] Sage Intacct - Authentication error reappears after disconnecting from Sage Intacct

[izarutskaya]

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.0.37-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+shsb22not112@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Create a new workspace
2. Enable accounting
3. Navigate to accounting page > Connect to Sage Intacct > Upgrade to control > Continue with the setup
4. Enter invalid credentials when prompted
5. While it is trying to connect, navigate away and come back to accountings page (Important)
6. Wait for the authentication error to appear
7. Once the error appears click on the three dot menu and click on "Disconnect"

Expected Result:

The workspace is disconnected from Sage Intacct connection and the authentication error disappears

Actual Result:

The authentication error reappears after disconnecting from Sage Intacct connection

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

Bug6607555_1726655865892.2024-09-18_13_35_37.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021836478663874327079
• Upwork Job ID: 1836478663874327079
• Last Price Increase: 2024-09-18

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

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

[izarutskaya]

production

Recording.2831.mp4

[izarutskaya]

We think this issue might be related to the #wave-control

[madmax330]

I think this is an app blocker and needs to be fixed on the front-end

[melvin-bot]

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

[github-actions]

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

[madmax330]

I'm also not able to repro on web in staging 😕

[grgia]

Wondering if this is a similar root cause to #49372 (comment)

[grgia]

Actually Im not able to reproduce either, going to demote as an app blocker.

[melvin-bot]

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

[melvin-bot]

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

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[trjExpensify]

I also can't repro this:

2024-09-19_01-04-52.mp4

@izarutskaya are there different steps to follow or can you re-test this?

[melvin-bot]

@trjExpensify, @parasharrajat, @stitesExpensify Eep! 4 days overdue now. Issues have feelings too...

[stitesExpensify]

I'm going to close this since nobody was able to repro