Repository navigation
Sage Intacct - Back button on workspace editor returns to Accounting page again #44813
Description
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: 9.0.4-0
Reproducible in staging?: Y
Reproducible in production?: N
Found when executing PR : #43661
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:
- User has a few workspaces.
- One of the workspaces is connected to Sage Intacct.
- Go to staging.new.expensify.com
- Go to another workspace that is not connected to Sage Intacct.
- Go to Accounting.
- Tap Connect next to Sage Intacct.
- Select Reuse existing connection.
- Tap on the workspace that is connected to Sage Intacct.
- Tap back button on the top left.
- Tap back button again.
Expected Result:
App will return to workspace list.
Actual Result:
App returns to Accounting page again (from Step 3).
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
Bug6532647_1720059749451.RPReplay_Final1720058908.mp4
Metadata
Metadata
Type
Projects
- Status
Activity
melvin-bot commentedon Jul 4, 2024
Triggered auto assignment to @twisterdotcom (
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.melvin-bot commentedon Jul 4, 2024
Triggered auto assignment to @lakchote (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 4, 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:
izarutskaya commentedon Jul 4, 2024
@twisterdotcom FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
izarutskaya commentedon Jul 4, 2024
We think this issue might be related to the #collect project.
lakchote commentedon Jul 4, 2024
cc @SzymczakJ since you've worked on #43661
20 remaining items
lakchote commentedon Jul 15, 2024
Not overdue, @hungvu193 commented above.
SzymczakJ commentedon Jul 16, 2024
Follow-up merged, this should be fixed 😄
melvin-bot commentedon Jul 18, 2024
@twisterdotcom @hungvu193 @lakchote @SzymczakJ this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
twisterdotcom commentedon Jul 18, 2024
Are we just waiting for a deploy now?
hungvu193 commentedon Jul 19, 2024
I think the PR that fixed this issue was deployed to staging, we can retest this and close if we can't reproduce
lakchote commentedon Jul 19, 2024
The PR that fixed it was actually even deployed to production
Asked for a QA retest here
twisterdotcom commentedon Jul 19, 2024
Okay, do we need to handle any payment here? Or will this be handled in #44669 then?
hungvu193 commentedon Jul 19, 2024
No payment needed here. We can close it.