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
Expensify Card - RHP closes instead of returning to profile after assigning card from profile #78262
Please re-state the problem that we are trying to solve in this issue.
Expensify Card - RHP closes instead of returning to profile after assigning card from profile
What is the root cause of that problem?
In IssueNewCardConfirmMagicCodePage, currently we're using Navigation.goBack(backTo) when a backTo parameter is provided. The goBack method attempts to go back in the navigation stack, but since the member details page and the magic code confirmation page are in different navigation contexts, calling goBack is causing the entire RHP to close.
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
This seems weird, the expected behaviour seems incorrect. @jponikarchuk I can't access the test in browserstack - are you able to add something that shows me that we'd expect this?
Activity
melvin-bot commentedon Dec 22, 2025
Triggered auto assignment to @RachCHopkins (
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.samranahm commentedon Dec 22, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Expensify Card - RHP closes instead of returning to profile after assigning card from profile
What is the root cause of that problem?
In
IssueNewCardConfirmMagicCodePage, currently we're usingNavigation.goBack(backTo)when a backTo parameter is provided. ThegoBackmethod attempts to go back in the navigation stack, but since the member details page and the magic code confirmation page are in different navigation contexts, callinggoBackis causing the entire RHP to close.App/src/pages/workspace/expensifyCard/issueNew/IssueNewCardConfirmMagicCodePage.tsx
Lines 36 to 42 in df5234b
What changes do you think we should make in order to solve the problem?
We should change
goBacktonavigatehere
App/src/pages/workspace/expensifyCard/issueNew/IssueNewCardConfirmMagicCodePage.tsx
Lines 36 to 42 in df5234b
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
melvin-bot commentedon Dec 26, 2025
@RachCHopkins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
RachCHopkins commentedon Dec 29, 2025
This seems weird, the expected behaviour seems incorrect. @jponikarchuk I can't access the test in browserstack - are you able to add something that shows me that we'd expect this?
jponikarchuk commentedon Dec 30, 2025
@RachCHopkins
The option to assign cards to members via the Members listis removed now #77798