-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] The active background screen changes after opening a contact method #47612
Comments
Triggered auto assignment to @kevinksullivan ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
@kevinksullivan |
Edited by proposal-police: This proposal was edited at 2024-08-19 02:01:08 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.The active background screen when going to contact method from I'm a teacher page changes to profile screen. What is the root cause of that problem?When we go to the contact method, getAdaptedStateFromPath is triggered to find the matching root for the contact method RHP. App/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts Lines 192 to 193 in 62722e8
Based on the App/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts Lines 138 to 145 in 62722e8
So, the profile page central screen is added because there is a state diff. App/src/libs/Navigation/linkTo/index.ts Lines 135 to 141 in 62722e8
But, we actually have a way to find the matching root based on the App/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts Lines 110 to 136 in 62722e8
When we go from I'm a teacher to a contact method, the
then use it as the
What changes do you think we should make in order to solve the problem?Call the get active route when pressing the button in
But this still isn't enough because even though the App/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts Lines 114 to 115 in 62722e8
App/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts Lines 123 to 129 in 62722e8
It's because Last, we need to also pass the App/src/pages/settings/Profile/Contacts/ContactMethodsPage.tsx Lines 93 to 94 in 62722e8
App/src/pages/settings/Profile/Contacts/NewContactMethodPage.tsx Lines 80 to 85 in 62722e8
|
@ZhenjaHorbach I don't see step 5. Is there anything missing from the reproduction steps? |
@kevinksullivan looking at the code logic, the step 5 will show if we use a public domain email as the default contact method. |
Job added to Upwork: https://www.upwork.com/jobs/~010a99315386621f72 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
Is @ZhenjaHorbach reviewing this one? |
@Ollyws |
@bernhardoj's proposal LGTM. |
Triggered auto assignment to @cristipaval, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
PR is ready cc: @Ollyws |
Due for payment tomorrow @kevinksullivan, Thanks! |
Payment summary:
|
Requested in ND. |
$250 approved for @bernhardoj |
Requested in ND. |
$250 approved for @Ollyws |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number:
Reproducible in staging?: Needs Reproduction (Reproduction attempt not made as its live)
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @ZhenjaHorbach
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1723753120436449
Action Performed:
Expected Result:
User should remain in the backgrounded
Save the world
pageActual Result:
Active backgrounded page changes to profile page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @OllywsThe text was updated successfully, but these errors were encountered: