-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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] Accounting – When navigate back from NetSuite page workspace profile page opens #46230
Comments
Triggered auto assignment to @stephanieelliott ( |
@stephanieelliott FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #vip-vsp |
ProposalPlease re-state the problem that we are trying to solve in this issue.Accounting – When navigate back from NetSuite page workspace profile page opens What is the root cause of that problem?We don't define the backTo param here:
What changes do you think we should make in order to solve the problem?We will add the third param pointing to policyAccountingPage. We will get it from Navigation.navigate(ROUTES.WORKSPACE_UPGRADE.getRoute(policyID, CONST.UPGRADE_FEATURE_INTRO_MAPPING.netsuite.alias, Navigation.getActiveRouteWithoutParams())); ResultScreen.Recording.2024-07-26.at.2.08.11.AM.mov |
ProposalPlease re-state the problem that we are trying to solve in this issue.Accounting – When navigate back from NetSuite page workspace profile page opens What is the root cause of that problem?We are not passing the App/src/components/ConnectToNetSuiteButton/index.tsx Lines 59 to 60 in b0f810d
so it will fallback to the workspace profile route here App/src/pages/workspace/upgrade/WorkspaceUpgradePage.tsx Lines 47 to 48 in b0f810d
What changes do you think we should make in order to solve the problem?We should pass the accounting route as the backTo here App/src/components/ConnectToNetSuiteButton/index.tsx Lines 59 to 60 in b0f810d
if needed we can also remove workspace profile fallback route here App/src/pages/workspace/upgrade/WorkspaceUpgradePage.tsx Lines 47 to 48 in b0f810d
What alternative solutions did you explore? (Optional) |
@stephanieelliott Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Job added to Upwork: https://www.upwork.com/jobs/~01564450f18c93f647 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
Hey @abdulrahuman5196 we've got a few proposals to review on this one! |
Checking now |
@neonbhai 's proposal here #46230 (comment) looks good and works well. Other proposals are similar. 🎀 👀 🎀 |
Triggered auto assignment to @robertjchen, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @neonbhai 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Let's do it 👍 |
Thank you for assigning, raising PR soon! |
Hey @neonbhai looks like the PR review is held on a comment looking from clarification from you -- can you weigh in when you get a sec? |
hi, I've run in an issue, when testing the upgrade workspace flow that affects navigation: Steps (Reproducible in prod):
Screen.20Recording.202024-08-09.20at.209.mp4We fix this by dismissing the upgrade page when over a chat (instead of falling back to workspace profile). Here: App/src/pages/workspace/upgrade/WorkspaceUpgradePage.tsx Lines 45 to 48 in 87c116b
onBackButtonPress={() => Navigation.goBack()} This will make the upgrade page go back only if navigation state has previous items, and to dismiss if user has an empty navigation stack (site reloaded) ResultThis works perfectly: Screen.Recording.2024-08-09.at.12.39.16.PM.movShould we fix this? 👍 - Agree, go ahead |
Hey @robertjchen what do you think of the proposal above? |
I think we should fix this, please proceed 👍 |
Hey @neonbhai checking in from this comment on the PR:
With this being the case, are you saying we should close this issue? Also, does that mean that the fix described here is no longer necessary? |
@stephanieelliott hi, yes the fix in #46230 (comment) was incorporated here in #45730. And since navigation connected to upgrade flow has changed, the approach in this PR is not necessary. We should close the issue |
Requesting compensation for the PR 🙇 |
This issue has not been updated in over 15 days. @robertjchen, @stephanieelliott, @abdulrahuman5196, @neonbhai eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Thanks @neonbhai! Makes sense, I agree we should issue payment for this and then close. |
Summarizing payment on this issue:
Upwork job is here: https://www.upwork.com/jobs/~01201199f64fde6026 |
Hi @stephanieelliott I am getting paid via newDot. Will request in newDot. |
Thanks! 🙇 |
$250 approved for @abdulrahuman5196 |
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: 9.0.12-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
User should land on Accounting page
Actual Result:
User lands on Workspace profile page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6553050_1721937459940.Recording__3588.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @abdulrahuman5196The text was updated successfully, but these errors were encountered: