You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-03-19] Admin seeing competing RBR paths with broken company card connection #81724
Version Number: Reproducible in staging?: Needs Reproduction (Reproduction blocked) Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from BrowserStack: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@joekaufmanexpensify Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Connect a direct feed and assign a card to the admin
Break the feed's connection
Expected Result:
Per this, the admin should see an RBR path directing them to the error on the company cards page. If they also have an assigned card, they should see an error on the card row on wallet, but not a full RBR path leading them to wallet. Only non-admin employees with an assigned card should see the RBR path leading them to the error on wallet.
Actual Result:
Workspace admin with assigned card on broken feed sees full RBR path leading them to the error on company cards AND on wallet.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
📣 @scerrato88! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Hey Chris, no worries, I asked @hungvu193 to work on this one to tackle more issues in parallel so you and I can focus on our other existing open issues 🙏
Currently, we show/hide the indicator based on whether the user is an admin of any workspace or not (isPolicyAdmin), but maybe we'll have to be specific with exact workspsace
Currently, we show/hide the indicator based on whether the user is an admin of any workspace or not (isPolicyAdmin), but maybe we'll have to be specific with exact workspsace
Oh I see. I remember I also concerned about it while reviewing the PR 😄. Let me take a look
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Feb 6, 2026
Triggered auto assignment to @jliexpensify (
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 Feb 6, 2026
📣 @scerrato88! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
chrispader commentedon Feb 7, 2026
@carlosmiceli i can tackle this. I should have a good idea where this needs to be fixed!
carlosmiceli commentedon Feb 7, 2026
Hey Chris, no worries, I asked @hungvu193 to work on this one to tackle more issues in parallel so you and I can focus on our other existing open issues 🙏
carlosmiceli commentedon Feb 7, 2026
Having said that, @hungvu193 please do ask Chris for pointers if it's hard to spot the solution 💪
hungvu193 commentedon Feb 8, 2026
@chrispader Yeah I would love to hear your idea about fixing the RCA 🙏
chrispader commentedon Feb 9, 2026
Alright, i'll let @hungvu193 handle this. @hungvu193 the issue should be located in the error states for workspace/account indicator in
useNavigationTabBarIndicatorChecks.ts.Currently, we show/hide the indicator based on whether the user is an admin of any workspace or not (
isPolicyAdmin), but maybe we'll have to be specific with exact workspsacehungvu193 commentedon Feb 10, 2026
Oh I see. I remember I also concerned about it while reviewing the PR 😄. Let me take a look
38 remaining items
jliexpensify commentedon Mar 19, 2026
Any checklist required here? Payment date is tomorrow
melvin-bot commentedon Mar 19, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
jliexpensify commentedon Mar 20, 2026
@hungvu193 @ShridharGoel any checklist required here?
hungvu193 commentedon Mar 20, 2026
We do yeah. @ShridharGoel Please complete the checklist when you have a chance. Thanks
twisterdotcom commentedon Mar 20, 2026
@hungvu193 has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-4110-a46c-e3c9-7e8683aa1a24ShridharGoel commentedon Mar 20, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: N/A
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/614411
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-3ebc-a99e-5f4b-80c949bc0e64mallenexpensify commentedon Mar 20, 2026
Thx @ShridharGoel
JmillsExpensify commentedon Apr 6, 2026
$250 approved for @ShridharGoel