Skip to content

Expensify Card - Member cannot see card details from link in workspace chat unless Wallet is opened #50471

Description

@lanitochka17

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.46-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+kh0610009@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. [Admin] Asssign a virtual card to member
  3. [Member] Do not go to Wallet page (important)
  4. [Member] Go to workspace chat
  5. [Member] Click on Expensify Card link
  6. [Member] Note that Expensify Card details are not revealed (limit and buttons) when opened from the link
  7. [Member] Go to Wallet
  8. [Member] Go back to workspace chat and open Expensify Card link
  9. [Member] Note that Expensify Card details are only revealed (limit and buttons) after user opens Wallet page

Expected Result:

In Step 6, member should be able to see their Expensify Card details (limit and buttons) without going to Wallet page

Actual Result:

In Step 6, member is not able to see their Expensify Card details. It does not show the limit and buttons are hidden
In Step 9, after opening Wallet page, user can see Expensify Card details from the link in workspace chat

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

Add any screenshot/video evidence
Bug6628452_1728400120105.20241008_230120.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Oct 8, 2024

    @melvin-bot

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

  2. github-actions commented on Oct 8, 2024

    @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.
  3. lanitochka17 commented on Oct 8, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave-collect - Release 2

  4. allgandalf commented on Oct 8, 2024

    @allgandalf
    Contributor

    @truph01 @jjcoffee related to your PR ? #50039

  5. truph01 commented on Oct 8, 2024

    @truph01
    Contributor

    @allgandalf I think it is bug 2 I mentioned here. BE should handle it by sending pusher data.

  6. allgandalf commented on Oct 8, 2024

    @allgandalf
    Contributor

    @truph01 lets talk in this slack thread

  7. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 8, 2024
  8. thienlnam commented on Oct 8, 2024

    @thienlnam
    Contributor

    Not a blocker from slack thread since this is not a common flow in NewDot, though should be fixed soon

  9. 1 remaining item

  10. truph01 commented on Oct 8, 2024

    @truph01
    Contributor

    @thienlnam This should be fixed in BE, right?

  11. added
    InternalRequires API changes or must be handled by Expensify staff
    on Oct 8, 2024
  12. thienlnam commented on Oct 8, 2024

    @thienlnam
    Contributor

    Yeah, looks like it can be - cc @mountiny for how to proceed on this

  13. mountiny commented on Oct 8, 2024

    @mountiny
    Contributor

    Gonna take over

  14. mountiny commented on Oct 14, 2024

    @mountiny
    Contributor

    I think this is already sorted as we started to push the onyx updates about new virtual cards correctly now

  15. mountiny commented on Oct 14, 2024

    @mountiny
    Contributor
  16. izarutskaya commented on Oct 14, 2024

    @izarutskaya

    Issue is not reproducible anymore.

    bandicam.2024-10-14.20-15-12-937.mp4
  17. mountiny commented on Oct 14, 2024

    @mountiny
    Contributor

    Perfect so that was fixed with the auth pr

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

Metadata

Metadata

Labels

DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions