Skip to content

[Due for payment 2026-01-05] Company cards-Not here page displayed after selecting an accounting credit card export option #78317

Closed

Description

@mitarachim

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.86-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: https://test-management.browserstack.com/projects/2219752/folder/13176706/test-cases/41236845
Email or phone of affected tester (no customers): applausetester+ccardfeed@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 10 / Chrome
App Component: Workspace Settings

Action Performed:

Pre-condition: Log in with an account with assigned company cards and link an accounting service (Quickbooks on this case)

  1. Go to Workspace > Company cards
  2. Select an assigned company card
  3. Click on "Quickbooks Online credit card export" field
  4. Select a different option
  5. After Not here page is displayed, go back
  6. Select the same field again

Expected Result:

Not here page should not be displayed. After selecting an option. the app should land on the card details page again with the selected option in the preview of the field.

Actual Result:

Not here page is displayed. After selecting an option and going back, the new option is displayed in the field preview, but when accessing again, the new option does not have the checkmark on the right side.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7035661_1766452504469.bandicam_2025-12-22_21-05-21-240.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

Activity

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

    @melvin-bot

    Triggered auto assignment to @sonialiap (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 23, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 23, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 23, 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. hungvu193 commented on Dec 23, 2025

    @hungvu193
    Contributor

    Taking a look 👀

  7. carlosmiceli commented on Dec 23, 2025

    @carlosmiceli
    Contributor

    @hungvu193 thank you!!

  8. 5 remaining items

  9. MonilBhavsar commented on Dec 23, 2025

    @MonilBhavsar
    Contributor

    Not related to API, so removing DeployBlocker label

  10. carlosmiceli commented on Dec 23, 2025

    @carlosmiceli
    Contributor
  11. m-natarajan commented on Dec 24, 2025

    @m-natarajan

    Not repro in Windows chrome v9.2.86-4

    Recording.2120.mp4
  12. hungvu193 commented on Dec 26, 2025

    @hungvu193
    Contributor

    We're good to close 😄

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 29, 2025
  14. changed the title [-]Company cards-Not here page displayed after selecting an accounting credit card export option[/-] [+][Due for payment 2026-01-05] Company cards-Not here page displayed after selecting an accounting credit card export option[/+] on Dec 29, 2025
  15. melvin-bot commented on Dec 29, 2025

    @melvin-bot

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

  16. 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. 🎊

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

    • @hungvu193 requires payment through NewDot Manual Requests
  17. melvin-bot commented on Dec 29, 2025

    @melvin-bot

    @hungvu193 @sonialiap 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